Closed
Bug 478339
Opened 16 years ago
Closed 14 years ago
create uniqueID from memory address of accessible
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: surkov, Unassigned)
References
(Blocks 1 open bug)
Details
nsIAccessNode::uniqueID is formed from memory address of DOM element this accessible is created for. Since some accessibles shares the same DOM node (like treeitems accessible for xul:tree) then uniqueID is not unique. I guess we should for uniqueID from memory address of this accessible.
Reporter | ||
Comment 1•16 years ago
|
||
I misread the code, now I see uniqueID should be unique for those accessibles that shares the same DOM node. I think we can simplify the code at this point and make uniqueID to be created from memory address of the accessible.
Blocks: cleana11y
Summary: uniqueID should be unique → create uniqueID from memory address of accessible
Comment 2•16 years ago
|
||
Aren't there still some handy keys based on things like row/col etc? Sorry this is a fly-by comment... based on some vague memories from tbird's email list.
Reporter | ||
Comment 3•16 years ago
|
||
(In reply to comment #2)
> Aren't there still some handy keys based on things like row/col etc? Sorry this
> is a fly-by comment... based on some vague memories from tbird's email list.
David, sorry I don't follow you. Could you explain in details?
Reporter | ||
Comment 4•15 years ago
|
||
Note, we can't easy turn to accessible address usage as a key because nsAccessibilityService::GetAccessible() check the document cache by DOM node as unique ID of the accessible.
Reporter | ||
Comment 5•14 years ago
|
||
it was fixed at some point
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•