Closed Bug 130298 Opened 24 years ago Closed 24 years ago

Does not select item in menu when using arrow keys

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 126379

People

(Reporter: ryan, Assigned: aaronlev)

References

()

Details

Attachments

(2 files)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311 BuildID: 2002031104 In the example page you will find that you can select on the fields with the mouse and it will do different things. If you change the fields with the arrow keys, it won't change the appropriate fields. Not sure if this is a javascript issue or just a browser issue. Reproducible: Always Steps to Reproduce: 1. Goto web page at http://www.nhorizon.net/~ryan/mozilla_bug1.html 2. Click on the field "category" 3. Use arrow keys to change the values, notice it doesn't change anything in other fields. (only changes the current field) Actual Results: The only field that changes is one that you're moving the arrow keys in. Expected Results: Mozilla should have done the javascript function that would have changed the other fields.
Same patch as above, but more space so that popup doesn't cover other form controls. It doesn't do anything for me script-wise whether I use the mouse or the keyboard.
Same patch as above, but more space so that popup doesn't cover other form controls. It doesn't do anything for me script-wise whether I use the mouse or the keyboard. What is it supposed to do exactly?
I am the one who requested Mozilla's current behavior (in bug 110800). The reason I asked for onchange to not fire right away is that web developers who use onchange often make the assumption that the user will never temporarily select the wrong item before selecting the item they intend to select. (This assumption is reasonable if the user selects an item using the mouse or if the user opens the dropdown menu with Alt+Down, but not if the user selects using just the arrow keys.) Onchange fires when the user moves focus from the dropdown, for example by pressing the Tab key or by clicking somewhere else in the document. If this turns out to be a major problem, we may reverse the change. I think that navigation remains the main use of <select size=1 onchange=*>, though, and having to hit tab to make the rest of a form update isn't as bad as not being able to navigate a site. (I'm testing http://www.nhorizon.net/~ryan/mozilla_bug1.html because I get JavaScript errors at the attached testcases.)
*** Bug 144174 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 126379 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
marking verified as a duplicate. if you decide to reopen this bug, please clarify why. search string for bugspam removal: SalviaGuaranitica
Status: RESOLVED → VERIFIED
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: