Closed
Bug 300780
Opened 19 years ago
Closed 19 years ago
Initial focus in rich list boxes should go to first item
Categories
(Firefox :: Keyboard Navigation, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
(Keywords: access)
Attachments
(1 file)
|
818 bytes,
patch
|
mconnor
:
review+
mconnor
:
approval1.8b4+
|
Details | Diff | Splinter Review |
When opening up the downlooad, extension or theme manager they focus should be on the first item in the list. This affects access with a screen reader as well.
| Assignee | ||
Comment 1•19 years ago
|
||
Screen reader users are in fact having issues with this dialog, especially after deleting a download.
Blocks: deera11y
Updated•19 years ago
|
Attachment #190357 -
Flags: review?(mconnor)
Attachment #190357 -
Flags: review+
Attachment #190357 -
Flags: approval1.8b4+
| Assignee | ||
Comment 3•19 years ago
|
||
Checking in richlistbox.xml; /cvsroot/mozilla/toolkit/content/widgets/richlistbox.xml,v <-- richlistbox.xml new revision: 1.9; previous revision: 1.8 done
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 4•19 years ago
|
||
There is code that stores the last selected item and probably attempts to select the last selected item in the Extension Manager. Why wasn't that removed when removing the ability for the last selected item to be the selected item when opening the Extension Manager?
Comment 5•19 years ago
|
||
Can you please tell me what was wrong when last selected item had focus and it had been scrolled into view ? FF 1.0 - last selected item has focus FF trunk (2005-06-18 - 2005-07-24) - last selected item has focus + it is scrolled into view FF trunk (2005-07-25 ->) initial focus is always on first item I'm seeing this bug as a step backward, it could be a workaround for FF 1.0 behaviour but not after Bug 245388 was fixed which is now broken by this bug. IMHO this feature was really important and you didn't have to have e.g. many extensions installed to acknowledge this.
| Assignee | ||
Comment 6•19 years ago
|
||
Yes if extension manager wants to implement its own focus memory it should be able to do that. Not sure why that's not working. Download manager didn't have that.
You need to log in
before you can comment on or make changes to this bug.
Description
•