Closed Bug 392243 Opened 17 years ago Closed 17 years ago

Reintroduce EVENT_REORDER for mutation events in MSAA

Categories

(Core :: Disability Access APIs, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: aaronlev, Assigned: aaronlev)

References

(Blocks 1 open bug)

Details

(Keywords: access, regression)

Attachments

(1 file)

Removing EVENT_REORDER caused a regression in JAWS' virtual buffer updates. Unfortunately we got the wrong information on that one.

Good catch, Marco.
Keywords: regression
Attachment #276693 - Flags: review?(ginn.chen) → review+
Can we do not reintroduce EVENT_REORDER event and to fire MSAA event in msaa code only?
Attachment #276693 - Flags: approval1.9?
Surkov, I like this solution best because it minimizes the number of EVENT_REORDERs that are fire. Or perhaps I don't understand your suggestion.
(In reply to comment #3)
> Surkov, I like this solution best because it minimizes the number of
> EVENT_REORDERs that are fire. Or perhaps I don't understand your suggestion.
> 

I suggested to live without reorder event in crossplatform code if we need it for msaa only. Therefore I asked can we handle gecko's create/destroy/show/hide events in MSAA only and fire event_system_reorder there? I didn't look at code, it's just a question.
We can't do it easily without firing double REORDER events for some changes.
Attachment #276693 - Flags: approval1.9? → approval1.9+
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Fix confirmed! Behaviour is back to what it was in Firefox 2.0, and content updates properly.
You need to log in before you can comment on or make changes to this bug.