User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Steps to reproduce:
Example HTML to reproduce: http://pastebin.com/5ExFWtT6
The button is disabled no matter how many times you refresh. You need to click in the URL bar and press enter to "really" reload the page with the button enabled.
The button should be enabled after a reload (F5, ctrl+r). This is how it works in all other browsers, e.g. Chrome. And it makes perfect sense for it to work that way.
Created attachment 559864 [details]
Testcase from the link.
Confirming on the testcase, Win XP.
Does this require jquery to reproduce?
Disabled state is persisted for buttons across a soft refresh, along with other form control state. I believe there are existing bugs on that.
Is it intentional?
We have code to make it explicitly happen, so yes.
The big question is whether it's desired. And the problem is that that depends on the use cases... If the button is disabled in response to the values of other inputs on the page, for example, then restoring those values should also restore the disabled state.
It's not consistent with other browsers. And if you ask me, the coder (JS) should take care of these things, not the browser itself. E.g. run validations on DOM load. There is just too many cases where this is not the desired behavior.
Dup Bug 654072
and Bug 277724,Bug 300364 ?
*** This bug has been marked as a duplicate of bug 654072 ***