Tab key should only reach Remove button for active item in Container tabs list
Categories
(Firefox :: Settings UI, defect, P5)
Tracking
()
People
(Reporter: MarcoZ, Assigned: Gijs)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [userContextId][domsecurity-backlog] )
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Assignee | ||
Comment 1•8 years ago
|
||
Updated•8 years ago
|
Updated•8 years ago
|
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Updated•2 years ago
|
Comment 7•2 years ago
|
||
The first problem reported in comment 0 appears to be fixed now: you can arrow up and down the list with no problems.
The second still exists: tab takes you through the remove buttons for each container, regardless of what container is active in the list. This is very confusing for a screen reader user and could potentially result in them removing the wrong container, which is pretty nasty.
This is similar to bug 1501897 and probably needs a similar fix; i.e. setting tabindex="-1" on buttons which aren't for the current item.
Assignee | ||
Comment 8•2 years ago
|
||
Rather than having each richlistbox consumer having to reinvent focus patterns for
buttons and menulists in its 'rich' items, let's just teach richlistbox and
richlistitem to not suck at keyboard navigation. That way we won't keep forgetting
to deal with this whenever we add new lists anywhere.
This allows us to remove the custom handling in sitePermissions.js, and the same
handling should be covered by the existing test, ie
browser/components/preferences/tests/browser_permissions_dialog.js
Updated•2 years ago
|
Comment 10•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Updated•1 years ago
|
Updated•1 years ago
|
Updated•1 years ago
|
Description
•