AXDOMClassList not supported on macOS
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
People
(Reporter: rafaeldeleao, Unassigned, Mentored)
References
Details
(Keywords: good-first-bug)
Attachments
(2 files)
Steps to reproduce:
on MacOS, Open Accessibility Inspector
Inspect a11y elements in a webpage
Actual results:
DOM Class is always empty
Expected results:
DOM Class displays the value as seem with the Web Developer Tools
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Reporter | ||
Comment 2•2 years ago
|
||
Comment 3•2 years ago
|
||
cc Morgan, can you give this a look on macOS? I don't have a mac and I'm not familiar enough with Accessibility Inspector to know off-hand. My first thought is that is should be hitting code in mozAccessible.mm and getting routed to RemoteAccessible::DOMNodeClass. I'm not sure how Accessibility Inspector queries this, but maybe something is off there.
Comment 4•2 years ago
|
||
I don't think we support DOMClass as an attribute -- if we did it'd be under "AXDOMClass" in the moxAccessible protocol. We do support AXDOMIdentifier here. This bug seems valid to me.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Marking as good-first-bug. Please use the need-info functionality to request my attention if you'd like guidance or mentorship in working on this :) thank you !
Updated•2 years ago
|
Comment 7•2 years ago
|
||
Bug 1912836 and this spec PR suggest this should be AXDOMClassList, rather than AXDOMClass.
Description
•