Closed Bug 1639399 Opened 4 years ago Closed 4 years ago

Expose unique ID to XPCOM.

Categories

(Core :: Disability Access APIs, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
mozilla78
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.

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.)

(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.

Pushed by yura.zenevich@gmail.com: https://hg.mozilla.org/integration/autoland/rev/d5cf77118989 expose uniqueID property on the xpcAccessible. r=Jamie
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: