Closed Bug 340972 Opened 18 years ago Closed 18 years ago

Accessibility events delayed until after native dialog is closed

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Version:
1.0 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla1.8.1beta2

People

(Reporter: aaronlev, Assigned: aaronlev)

References

Details

(Keywords: access, fixed1.8.1, regression) 

If you test with a screen reader or Accessible Event Watcher from the MSAA SDK, you will see menuend events fired when the user leaves the menubar, except when the a native dialog is opened. For example, after File -> Open, the menuend event is delayed until after the native dialog closes. This causes screen readers to not be able to read the dialog.

My current plan for fixing this involves adding interface methods to nsIAccessibilityService, to indicate menu status. The current usage of DOM events doesn't work, unless there is a way to keep the events safe *and* have them get fired before the native dialog opens.
Depends on: 339237
Flags: blocking1.9a1?
Flags: blocking-firefox2?
Component: Disability Access → Disability Access APIs
Flags: blocking-firefox2?
Product: Firefox → Core
Version: unspecified → 1.0 Branch
Flags: blocking1.8.1?
Assignee: nobody → aaronleventhal
Keywords: regression
Status: NEW → ASSIGNED
QA Contact: disability.access → accessibility-apis
Flags: blocking1.8.1? → blocking1.8.1+
Target Milestone: --- → mozilla1.8.1beta2
This was fixed by checkin to bug 339237. Will need that on branch to get the fix there too.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Keywords: fixed1.8.1
Flags: blocking1.9a1?
You need to log in before you can comment on or make changes to this bug.