I can confirm that 3.2.5 is the latest version that does not have this issue with the current version of WordPress. I can also tell you that the issue is with the removeAttribute method on line 151 of popup.php. Even when file.value evaluates as true, the “disabled” attribute is not being removed from the input button on the form. Still not sure if it is a browser or WordPress issue though.
Update: I am now 90% convinced this is due to changes in the JavaScript optimization engine of later Chromium-based browsers. I did some testing with some dummy PHP files and had similar results. Setting and removing DOM attributes seems to be not reliable anymore. I even added sleep functions as long as 20 seconds and still had issues (even after clearing the browser cache). Searching on other forums showed this is a common issue lately with the V8 engine. So I don’t think it is WordPress. I even tried removing the attribute altogether, adding a JS sleep function and then setting the disabled attribute after a couple of seconds. In theory, this should have worked, but instead the button remained enabled and the setAttribute method had no effect. This has to be a browser bug. There are other methods for setting and removing attributes. If I get the time later I will try some of them, but I’m done for the day.
-
This reply was modified 5 years, 11 months ago by
adotson.