472810 - incorrect order of a11y events for nsIDOMNode.replaceChild

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[alexander :surkov (:asurkov)]

nsIDOMNode.replaceChild don't produce remove/create/reorder a11y events. It seems order of these events may be different from time to time and some of events may be not fired.

Comment 1

[alexander :surkov (:asurkov)]

actually what happens:

1. there is no accessible and therefore there is no hide event
2. however there is reorder event
3. accessible is created when new node is appended therefore there is show event
4. and reorder event which is coalesced with first reorder event

so we have reorder and then show events. Eventually we should have show + reorder event. In the case when there is an accessible initially then we want to get hide + show + reorder. In the meantime reorder event will be fired between them.

Comment 2

[David Bolter [:davidb] (NeedInfo me for attention)]

Why does AT want the show event before the reorder event?

Comment 3

[alexander :surkov (:asurkov)]

possibly it doesn't matter but I think it's better to be consistent.

Comment 4

[David Bolter [:davidb] (NeedInfo me for attention)]

OK this makes sense. Sounds like it might be tricky to ensure the ordering during coalescing. I wonder if it would be safe to just push all reordering to the end of the queue.

Comment 5

[alexander :surkov (:asurkov)]

fixed by bug 570275