GNOME Bugzilla – Bug 653656
firefox starts out inaccessible (assuming default home page)
Last modified: 2011-06-29 20:12:09 UTC
Initially reported as ubuntu bug <https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/802926>, against gnome-orca 3.0.0-0ubuntu2. Reproduced using orca from Git, version ORCA_3_1_2-13-g5812b1c. Could be either orca (scripts) or firefox; I don't really know. Playing with debug.log, nothing jumped out at me as saying this is firefox's fault. 1. Close all firefox windows. 2. Start firefox with the default home page, about:home or pass this URL manually - run "firefox about:home". file: URLs also seem to have the same effect. Remote URLs don't - perhaps a timing issue? 3. Orca does not read the window title. It does not read any content. It does not respond to Orca keyboard shortcuts e.g. ins+tab won't tab between form controls (it will just act as normal tab). 4. As soon as you navigate firefox to a different page, or just refresh the current one by hitting F5, it will become accessible. Orca will work properly, e.g. Orca will immediately start reading stuff out, ins+tab will tab between form controls only, etc.
Firefox version is 5.0+build1+nobinonly-0ubuntu0.11.04.2. I haven't tested upstream firefox. I can only find 32-bit binaries for firefox, and I don't have the 32-bit versions of the accessibility libs installed. However, I was able to reproduce it even after disabling both of the custom Ubuntu firefox extensions (Ubufox, and the Mac OS style menu-bar-at-top-of-screen extension).
I'm pretty sure this is a firefox/gecko bug in which we're failing to get a needed event telling us we have any content to present -- an event we used to get. Assigning to Trev.
(In reply to comment #2) > I'm pretty sure this is a firefox/gecko bug in which we're failing to get a > needed event telling us we have any content to present -- an event we used to > get. yeah, I'm not the one to ask about the details, but apparently there was some combination of app settings and window managers taht could cause us not to get the events we use to see the document has loaded and we should start fireing accessibility events, but we recieved the events on a document reload. anyway this should be fixed by bugzilla.mozilla.org/show_bug.cgi?id=639835 > Assigning to Trev. and closing as fixed since this should already work with current nightly builds.