310350 - context menus don't work with screen readers starting on 09/21

Status: RESOLVED FIXED

(Firefox :: Disability Access, defect)

Description

[Dan Kinnunen]

Aaron noticed that the context menu stopped working on the latest FF build which
is 09/26 build.

steps to recreate:

1. Bring up Window Eyes and FF nightly build of 09/24 and using goggle.com
2. press * on the num key pad and you will noticed that nothing is spoken no
firing of events.

This working fine with 09/213 build.

Comment 1

[Dan Kinnunen]

Update, FYI this also broken with JAWS so we know it's a FF bug

Comment 2

[Aaron Leventhal]

We're no longer seeing popupshown events internally.

Comment 3

[Aaron Leventhal]

This was caused by bug 307172.

Comment 4

[Aaron Leventhal]

(In reply to comment #3)
> This was caused by bug 307172.

I was wrong. It was caused by adding
AreAncestorViewsVisible() as a requirement for creating accessibles.

Comment 5

[Aaron Leventhal]

Attachment: 1) Mark chrome docs as loaded so that mutation handling works, 2) Keep menu event impls separate for XUL vs. DHTML menus, 3) Use FireDelayedToolkitEvent for popupshown so ancestor views are visible

Comment 6

[Aaron Leventhal]

This also fixes the asymmetrical menu events that were occuring as a user typed
in an autocomplete such as the location bar. They're symmetrical now with this
patch, so the screen readers won't have to work around that issue anymore.

Comment 7

[Asa Dotzler [:asa]]

Comment on attachment 197872 [details] [diff] [review]
1) Mark chrome docs as loaded so that mutation handling works, 2)  Keep menu event impls separate for XUL vs. DHTML menus, 3) Use FireDelayedToolkitEvent for popupshown so ancestor views are visible

approved, pending brian's SR

Comment 8

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1527381