Open
Bug 129840
Opened 22 years ago
Updated 2 years ago
Form Popup elements keep focus if used with the mouse
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
NEW
People
(Reporter: mhaecker, Unassigned)
References
()
Details
(Keywords: helpwanted)
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.9+) Gecko/20020308 BuildID: 2002030803 When I use a for element (a pupup menu) with the mouse it keeps the focus after using it. So when I want to use keyboard navigation afterwoards its useless, because I really change the selected item in the menu. :( Reproducible: Always Steps to Reproduce: 1. Go to http://www.mozilla.org/quality/help/bugzilla-helper.html 2. Change one of the popup menus with the mouse 3. Try to move around on the page with the arrow buttons. Actual Results: Another item in the popup is selected Expected Results: The Page should move around. :)
Comment 1•22 years ago
|
||
This is, I believe, as-designed... You would want to unfocus the <select> using tab....
Reporter | ||
Comment 2•22 years ago
|
||
I dont know how this is handled on other plattforms (ive got a mac), but on Macs this is deffinitely wrong behavior (Its defined this way in the HIG AFAIK). The reason for this I dont know, but I think it may have something to do with mixing mouse and keyboard acces to the interface. For me its clear, when I use the browser, I dont have a scrollwheel (notebook), and use the keyboard to do most of the scrolling (spacebar and arrows), and the mouse to use the interface, so I deffinetely dont want to mix it. Or in other words, I do want a consistant interface that doesnt change the meaning of my keycomands every few seconds. :( thx alot Martin
Comment 4•22 years ago
|
||
couldn't have less to do with me. -> html form controls
Assignee: pinkerton → rods
Status: UNCONFIRMED → NEW
Component: Keyboard Navigation → HTML Form Controls
Ever confirmed: true
QA Contact: sairuh → madhur
Updated•22 years ago
|
QA Contact: madhur → tpreston
Updated•22 years ago
|
Priority: -- → P2
Target Milestone: --- → Future
Comment 6•22 years ago
|
||
URL invalid now. Reporter, can you still reproduce using an updated URL?
Comment 7•21 years ago
|
||
This bug is targeted at a Mac classic platform/OS, which is no longer supported by mozilla.org. Please re-target it to another platform/OS if this bug applies there as well or resolve this bug. I will resolve this bug as WONTFIX in four weeks if no action has been taken. To filter this and similar messages out, please filter for "mac_cla_reorg".
Comment 8•21 years ago
|
||
To keyboard nav, but again, right now we have behavior consistency -- no matter how you focus a combobox, keyboard commands on it will do the same thing. I'm not sure why we would want to change that....
Assignee: dcone → aaronlev5
Component: Layout: Form Controls → Keyboard: Navigation
Priority: P2 → --
Target Milestone: Future → ---
Here's what i'd suggest we do... [Note that it isn't designed to please anyone.] There's a preference, Edit>Preferences>Advanced>Keyboard Navigation - Tab Key Navigation - When Tab or Shift-Tab is (sic?) pressed, move between: [x] Links [x] Buttons, radio buttons, checkboxes, and lists Note: text boxes are always part of the tabbing order. I'd suggest that click only affect keyboard focus if it's to a tabable control. On Mac OS (X) some of the checkboxes above are not checked by default. This would mean that linux and windows users wouldn't notice any change, but mac users might be less annoyed (maybe).
Comment 10•20 years ago
|
||
Since Mozilla is no longer supported on Mac OS X pre-OS X might I suggest that this bug be changed to OS X as it also exist with Mozilla 1.4
Updated•20 years ago
|
Keywords: helpwanted
Comment 12•15 years ago
|
||
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Updated•15 years ago
|
QA Contact: tpreston → keyboard.navigation
Assignee | ||
Updated•5 years ago
|
Component: Keyboard: Navigation → User events and focus handling
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•