Closed Bug 499053 Opened 15 years ago Closed 14 years ago

Firing EVENT_OBJECT_HIDE on the parent is not ideal

Categories

(Core :: Disability Access APIs, defect)

All
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: davidb, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

We currently fire MSAA EVENT_OBJECT_HIDE on the parent of dom node that is going away (EVENT_DOM_DESTROY). The related code is in: nsAccessibleWrap::FirePlatformEvent (accessible/src/msaa/nsAccessibleWrap.cpp) One example where this is a problem for screen reader devs is when implementing the announcing of live region removals.
Jamie, Mick, how do you guys do it?
I think this is a dupe of bug 493531
Yeah, I see they might share a common solution, but I'm not sure I fully understand bug 493531.
Depends on: 494109
(In reply to comment #1) > Jamie, Mick, how do you guys do it? Do you mean how do we handle live region removals? If so, currently, we don't at all. :)
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 (bug 494109), and do whatever updating we need (cache etc), after we've fired our events.
it sounds we have three bugs with different summaries and different approaches (bug 493531 and bug 494109) for one issue that should have been fixed in bug 570275. David, please check if this bug has gone, I can't since you're not sure this bug is dupe of bug 493531, so I don't have clever idea what this bug is about :)
Can't remember... closing incomplete.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.