494109 - keep accessibles alive until event is fired

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[alexander :surkov (:asurkov)]

the scenario is
1) add child node
2) remove previous child node
3) parent accessible is invalidated (because we got add DOM node event)
4) removed accessible has no parent

I think it leads to bug 493531.

We definitely need to keep accessible alive until we fired event, otherwise if AT needs something more on hide event than its cache invalidation then it will fail.

Comment 1

[alexander :surkov (:asurkov)]

List of bugs might be affected by this fix: bug 412931, bug 408997, bug 394493, bug 405679, bug 397112, bug 398021.

Comment 2

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

This bug sounds right. Do you have a plan/wip?

Comment 3

[alexander :surkov (:asurkov)]

no plans, no wips just few tries and one problem keeps another one.

Comment 4

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

I think we can use the recent work on bug 467144 for this. Check to see if the removal is in a live region, and save the data we need, and do whatever updating we need (cache etc), after we've fired our events.

Comment 5

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

Sorry last comment was really meant for bug 488053

Comment 6

[alexander :surkov (:asurkov)]

This bug should have been fixed by bug 570275. Need to check.

Comment 7

[alexander :surkov (:asurkov)]

(In reply to comment #6)
> This bug should have been fixed by bug 570275. Need to check.

confirm fixed.