Expose unique ID to XPCOM.
Categories
(Core :: Disability Access APIs, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox78 | --- | fixed |
People
(Reporter: yzen, Assigned: yzen)
Details
Attachments
(1 file)
There's really no way reliable way ATM to identify an accessible uniquely. This will help with looking up or matching accessible objects/actors/snapshots in the accessibility tools. And potentially will be useful/helpful with some sort of future utility of looking up accessibles based on unique id.
Assignee | ||
Comment 1•4 years ago
|
||
Comment 2•4 years ago
|
||
You're probably aware of this already, but one important thing to note is that a core unique id is only guaranteed to be unique per document. You can't guarantee that there won't be an id conflict even in a sub-document because that sub-document might be OOP. (Windows ids are unique even across documents, but that is Windows specific and not exposed to core.)
Assignee | ||
Comment 3•4 years ago
|
||
(In reply to James Teh [:Jamie] from comment #2)
You're probably aware of this already, but one important thing to note is that a core unique id is only guaranteed to be unique per document. You can't guarantee that there won't be an id conflict even in a sub-document because that sub-document might be OOP. (Windows ids are unique even across documents, but that is Windows specific and not exposed to core.)
I think that should be fine. I think we can uniquely identify them along with having a matching browsing context ID or something similar.
Comment 5•4 years ago
|
||
bugherder |
Description
•