Closed Bug 1455135 Opened 6 years ago Closed 4 years ago

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

Categories

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

Product:
Core
Component:
Disability Access APIs
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: surkov, Unassigned)

Details

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.
Summary: get rid of unattached form tree tree state of accessible objects → get rid of unattached from tree tree state of accessible objects
Jamie, pls let know, when you confirm with vendors the change is safe
Flags: needinfo?(jteh)
Summary: get rid of unattached from tree tree state of accessible objects → get rid of unattached-from-tree state of accessible objects
(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.
Priority: -- → P3

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

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(jteh)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.