User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 When you enter the Filter Rules dialog, and start tabbing through the fields, the next tab stop after "Match any of the following" is a box containing the three table fields below (see image attachment). This is irrititating. Also, when in a List, you cannot select the item you want a tab your way out, because the field will default back to its initial value. It seems that the interface is optimized to be used with a Mouse, but it is not being tested by keyboard people like me. Reproducible: Always Steps to Reproduce: 1. Open Filter Rules Dialog 2. Tab through the fields Actual Results: The container box get selected as part of the tab stops. Expected Results: The container box SHUOLD NOT get selected as part of the tab stops.
(In reply to comment #0) > When you enter the Filter Rules dialog, and start tabbing through the fields, > the next tab stop after "Match any of the following" is a box containing the > three table fields below (see image attachment). This is irrititating. xref bug 185585. Where should the focus go if there are no items in the list? Or is it OK to put the focus on the box if there are no items? > Also, when in a List, you cannot select the item you want a tab your way out, > because the field will default back to its initial value. For the boxes in this dialog, if I open the dropdown (Alt-Down, F4 or on Aviary builds, a simple down-arrow) and then scroll down the list, tabbing loses the selection. You have to press Enter to accept the new value, then Tab. I don't know if there's a bug about this, it's a hard one to search for. (Look under Core: XP and Widget categories.) If I use a current trunk build (see bug 267101), simple Up- and Down-arrows, or initial letters of the value items, cause the value to scroll or change -- and with this change made, if I tab off the list following that, the change stays put.
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: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.