Closed
Bug 286872
Opened 20 years ago
Closed 19 years ago
Pressing "enter" to close a message window also sends "enter" keystroke to webpage behind it.
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: steves, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Type in a User ID on the webpage and hit "Enter". A window pops up explaining that you didn't type in a password. The "OK" button of that window is selected, and so hitting "Enter" again should close it. That single keystroke both closes the window, and tries to log into the webpage again, causing the same error window to appear again. Clicking "OK" with the mouse brings you back to the webpage, as expected. Trying the exact same sequence of events in IE works as expected. Reproducible: Always Steps to Reproduce: 1. Go to https://secure.netbank.com/login.htm 2. Type any User ID 3. Hit "Enter" 4. Message box should appear. Hit "Enter" again. Actual Results: Message box explaining a lack of a password should appear. Message box closes and then reappears repeatedly with each press of the "Enter" key, since Firefox handles it as 2 successive keystrokes. Expected Results: "Enter" key should close message box, not open a new one, and allow you to type in your password and try again.
This appears to be a bug in the webpage rather than Firefox. NetBank checks onkeyup whether you just hit the Enter key by calling SubmitOnEnter(). When you press the Enter key to clear the dialog, the dialog goes away, and when you release it the webpage sees a keyup event. Recommendations: NetBank should change their JavaScript to onkeypress rather than onkeyup. This bug is likely INVALID since it's not a Firefox bug.
Updated•20 years ago
|
Severity: minor → normal
OS: Windows XP → All
Hardware: PC → All
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•