1455135 - get rid of unattached-from-tree state of accessible objects

Status: RESOLVED WONTFIX

(Core :: Disability Access APIs, enhancement, P3)

Description

[alexander :surkov (:asurkov)]

Before we shutdown an accessible object, we deattach it from the tree, then fire hide event, and then destory it. This scenario was used by ATs, processing events in-process, to be able to fetch extra info, which shouldn't be the case in e10s world. So we can simplify the logic and kill accessible objects without delay.

Comment 1

[alexander :surkov (:asurkov)]

Jamie, pls let know, when you confirm with vendors the change is safe

Comment 2

[alexander :surkov (:asurkov)]

(In reply to alexander :surkov from comment #1)
> Jamie, pls let know, when you confirm with vendors the change is safe

It's not so easy, since we depend on the behavior internally. When we receive a 'remove' notification, then we deattach accessible from the tree, and then asynchronously fire hide and other events like menupopup_end, and we rely on non defunct accessible.

So advantages are not so evident as I thought initially - we indeed can save cycles if we avoided double tree traversals, however, that means we should move event processing before the event coalescence, which also means extra work potentially.

Comment 3

[James Teh [:Jamie]]

I don't think this is worth doing given comment 2.