Closed Bug 1479177 Opened 7 years ago Closed 3 years ago

Conflict of role attributes of AccessibleNode

Categories

(Core :: Disability Access APIs, defect, P3)

Product:
Core
Component:
Disability Access APIs
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: dora.tokio, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Actual results: (This bug is from https://bugzilla.mozilla.org/show_bug.cgi?id=1468110#c65) The role attribute newly added to AccessibleNode conflicted with the one already existed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: weba11y
Priority: -- → P3

AccessibleNode is from an old version of the AOM spec. It's possible we may need something similar when we get to virtual a11y nodes, but until that is actually specified, we really have no idea. Closing for now.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.