Closed
Bug 671573
Opened 14 years ago
Closed 8 years ago
Exposing the accessible keyboard shortcut for a child of button is redundant.
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: davidb, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
166 bytes,
text/html
|
Details |
Vendor reported.
I think this was recently noticed because we stopped pruning our tree for buttons.
|
Reporter | |
Updated•14 years ago
|
|
|
Reporter | |
Comment 1•14 years ago
|
||
Vendor reports the issue is with double-speaking the access key.
|
||
Comment 2•14 years ago
|
||
for HTML:input@type="button" we could not create accessible children at all, for HTML:button it shouldn't work (because of name computation for example or text interface support), for that buttonmenu or buttondropdown role looks reasonable so that pushbutton is pruned while menubutton is not.
|
|
Reporter | |
Comment 3•8 years ago
|
||
Closing as part of a batch cleanup of old untouched bugs. This bug hasn't been touched for at least 2000 days.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•