State change events for focus causing extra document loads in Window-Eyes

RESOLVED FIXED

Status

()

Core
Disability Access APIs
--
major
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Aaron Leventhal, Assigned: Aaron Leventhal)

Tracking

({access})

Trunk
access
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

11 years ago
We fire state change events when a the focus changes.

Unfortunately MSAA state change events don't come with event data to show what state changed. The screen readers look for state change for the STATE_BUSY state on a document to determine when a document is starting to load or is finished.

As a result, even just going to the menubar and hitting Escape is causing Window-Eyes to reload the page.

We should fix this by only firing the state change for focus events in ATK.
(Assignee)

Comment 1

11 years ago
Created attachment 269641 [details] [diff] [review]
Map ATK focus events to state change events, not at cross-platform nsIAccessible level
Attachment #269641 - Flags: review?(ginn.chen)

Updated

11 years ago
Attachment #269641 - Flags: review?(ginn.chen) → review+
(Assignee)

Updated

11 years ago
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.