GNOME Bugzilla – Bug 626154
Context menus do not work in Firefox 4.0
Last modified: 2011-01-09 19:07:43 UTC
Open a late version of Firefox Beta version 4.0 and pull up a page with any number of links. Tab or cursor to any normal link on the page and open the context menu by either hitting the context key to the right of the spacebar or by pressing Shift+F10. Expected results: the menu items would be spoken when pressing up and down arrow keys. Current results: Orca speaks nothing when using the arrow keys. Note that this works fine with earlier versions of Firefox.
> Note that this works fine with earlier versions of Firefox. Hmmmm. I wonder what they changed? <smile> Debug.out would be nice. And if it's a Firefox/Gecko bug, it would be great if you could file it in the Mozilla bugzilla and block this bug against it. Ditto for the unavailable/grayed bug you filed a couple of weeks ago. The core Orca team is focused on Orca bugs and Orca features in the "final stretch" of the GNOME release cycle. Things broken/changed by some other team in a non-GNOME module will eventually wind up on our to-do list, but I'm afraid they're back-burner at the moment. We could seriously use your help and the help of other community members in dealing with Firefox issues. Thanks!
Created attachment 167271 [details] Debug output using Firefox 4.0 beta3 I found a link on the start page and tabbed to a link; I then pressed the menu key and then proceeded to press the down arrow key 5 times and heard silence.
Created attachment 167272 [details] Debug output taken while using Firefox 3.5.9 I followed similar steps using this older version of Firefox and the context menus do speak properly. I see accessible name events being spoken when down-arrow was pressed each time and the menu items did speak.
With the nightly build of Firefox 4.0b7pre from Oct 4th, the menu problems sited in this bug seem to have been fixed. I just checked out context menus on both a normal link on a page and in the bookmarks library and they both talked as expected. Hopefully if they don't break anything with this in the future, we could probably consider this bug to close. I updated the bug I created on the Mozilla page with the same good news.
this still works is there a reason not to close this?
I don't see one. Thanks!