Closed Bug 532021 Opened 15 years ago Closed 8 years ago

when XUL tree item is collapsed/expanded then a11y mutation events aren't fired properly

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: surkov, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: access, Whiteboard: [auto-closed:inactivity]) 

Since XUL tree has flat structure then we should fire reorder event on the tree accessible and show/hide events on shown/hidden tree item accessibles.
Probably we shouldn't fire hide events when they are collapsed and destroy accessibles, we could mark them invisible and fire state change events or collapsed state change event on the parent. The problem can appear with lazy calculated/updated tree views. However this is something that should be considered and kept in mind.
AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [auto-closed:inactivity]
You need to log in before you can comment on or make changes to this bug.