Closed
Bug 443289
Opened 18 years ago
Closed 12 years ago
Buttons stays disabled after 'Go back one page' action
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: benjamin, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Buttons on webpage that are beeing disabled by Javascript on clicked(in order to prevent the submission of forms 2 or more times) stays disabled in the event that someones prend the 'Go back one page' button of the browser.
Reproducible: Always
Steps to Reproduce:
1.Fill de form
2.Press back button
3.Try to submit form again (impossible since button disabled)
Comment 1•18 years ago
|
||
May be a wanted issue by website author. Definitely not an accessibility issue, reassigning to different component.
Component: Disability Access → General
QA Contact: disability.access → general
Comment 2•18 years ago
|
||
This could be a duplicate of Bug 316838.
Component: General → History: Session
Product: Firefox → Core
QA Contact: general → history.session
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
Comment 3•14 years ago
|
||
Is anyone currently working on implementing this fix? I am working on a bug fix in which a store submit button needs to disable on first click to avoid multiple submissions of the same order. However, the button stays disabled if a user returns to the page with the back button...
Comment 4•14 years ago
|
||
Also, until this is implemented, do any of you know a workaround for this?
Comment 5•14 years ago
|
||
As a workaround you could try setting autocomplete="off" on the button. See bug 671466 for a similar bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•14 years ago
|
Comment 6•14 years ago
|
||
Thanks!
I also found a workaround at https://developer.mozilla.org/en/Using_Firefox_1.5_caching#section_5 which uses unload to fix the bug:
window.addEventListener('pageshow', PageShowHandler, false);
window.addEventListener('unload', UnloadHandler, false);
function PageShowHandler() {
window.addEventListener('unload', UnloadHandler, false);
}
function UnloadHandler() {
window.removeEventListener('unload', UnloadHandler, false);
}
Comment 7•12 years ago
|
||
404
Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•