User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030218 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030218 Using the keyboard to navigate a drop down listbox. Expected Results : Pressing a key ("C") that matches the first character of a line item jumps focus to that line ex. "Cat", "Canary", "Camel". Pressing that key mulitple times will step through all the lines that start with that character in sequence. Problem : Pressing a two different keys quickly does not navigate focus to the second line. Focus is moved to the first line, but it is not moved from there to the second line unless you wait 2-3 seconds between keystrokes. Another symptom - sometimes a key takes you to a line that does not start with that character. press H - jumps to "Hedgehog" wait 2 seconds press R - jumps to "Rabbit" quickly press H - jumps to "Rhino" Testcase : listbox.html <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>Drop down Listbox</title> </head> <body> Listbox: <br> Click on the pulldown arrow and the list should drawn. All 12 animal names should be listed from Dolphin to Shark. <br> <select> <option>Dolphin</option> <option>Dog</option> <option>Cat</option> <option>Hedgehog</option> <option>Rabbit</option> <option>Mouse</option> <option>Elephant</option> <option>Dove</option> <option>Rat</option> <option>Rhino</option> <option>Beaver</option> <option>Shark</option> </select> </body> </html> Reproducible: Always Steps to Reproduce: 1. 2. 3.
Actually, if you type "rh" quickly it will take you to the entry starting with "rh" if such an entry exists. And this is entirely purposeful -- it allows much faster navigation in listboxes. The ont issue, perhaps, is that we should not be sticking at "Cat" if in that testcase someone presses "c" and then "r" quickly, since there are no entries starting with "cr".
Severity: blocker → normal
OS: Windows 2000 → All
Hardware: PC → All
So is this invalid? Seems like it is.
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/
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
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.