Closed
Bug 377288
Opened 18 years ago
Closed 18 years ago
Ensure layout notifactions of visibility changes for Javascript accessibility UA's
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
DUPLICATE
of bug 357583
People
(Reporter: aaronlev, Assigned: aaronlev)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Spinoff from bug 376924
If the accessibilityService is initialized in any way, it needs to tell JS that it's active.
Also IsAccessibilityActive() should use a static global to track this, so that different presShells all agree on whether accessibility is active or not.
Comment 1•18 years ago
|
||
Aaron, in bug 376924 you removed GetFrame() methods from HTMLTextAccesible and HTMLBulletListAccessible. I guess nsAccessible::GetFrame and removed GetFrame() may return different frames. I suppose for list bullet should be returned frame for li. Neil guessed that multiline text node may have several frames, therefore removed GetFrame() and nsIAccessible::GetFrame() may be not one and the same.
Assignee | ||
Comment 2•18 years ago
|
||
Multiline test node will return primary frame, which is the one we kept. That should be the same, so I don't see a problem there.
For List bullet accessible it is a problem for list bullet bounds. The list bullets are broken anyway for things like character bounds. It's not as big of a problem as the crashing. Because character bounds were wrong anyway I think we need to look at list bullets and their frame usage anyway. Will you file a bug to deal with list bullet bounds and any other usage of frame?
Assignee | ||
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•