Closed Bug 538596 Opened 16 years ago Closed 14 years ago

button is disabled on page refresh, situation occurs with Mozilla Firefox only

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
3.5 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: cristi_jujea, Unassigned)

Details

(Whiteboard: [CLOSEME 2011-2-25])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) I am a web developer and the bug I found does not happen in other browsers. This is part of the html page : <div id="existingUserAccount" class="subsection"> ... <p id="logoutInfo">For security reasons, please log out when you are finished shopping: <button id="userLogoutButton" onClick="logUserOut()">Logout</button></p> </div> The problem is that the button is disabled as a result of the page refresh action triggered by the end user. It is true that the bug occurs when the end user follows certain steps before refreshing the web page, but this does not happen with other browser and the code for all the user steps is too long to upload. If you do need the code for each of the user steps please let me know. If you need more details, please let me know Reproducible: Always
Can you retest in safe-mode / with a new profile (this to exclude extension problems and profile corruptions) and with the latest 3.6 test build: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.2/ If it still happens can you provide a minimal testcase or at least a link to the page?
Version: unspecified → 3.5 Branch
I encountered the same problem. If I click on the button and then refresh the page the button is disabled when the refresh is completed even though nothing on the page changed. Clearing the cache with Ctrl-F5 re-enables the button but it is disabled again after a regular refresh. I did some experimenting and found that it only happens with button elements with no type attribute or the type attribute set to submit. I got the same results in Safe Mode as well. I was unable to reproduce the bug by simply creating an empty HTML file with just buttons.
The bug still present in Firefox 3.6.2, Windows XP. Using this code sample: <button onclick="this.disabled = 'disabled'; return false;">Disable Me</button> Click the button to disable it. After the button is disabled, refresh the page and the button stays disabled. Works fine on other browsers.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
I can reproduce this with Firefox 11, Linux, fresh profile in safe-mode using the code sample from comment 4. In my application the same happens to an input field. More precisely only the first input field is disabled after reload, but works again when reloading the page with Ctrl+F5. So it's not only BUTTON elements, but in my case it's always the first element of a form. When inspecting the HTML source of the page 'disabled=""' is added to that input element and I verified that this isn't delivered by the server.
I've the same problem. The problem disappear when the input is set with autocomplete="off"
This issue still exists, but I am not able (or don't know how) to remove the CLOSEME tag and mark the bug against a particular version.
You need to log in before you can comment on or make changes to this bug.