GNOME Bugzilla – Bug 492740
Orca doesn't read XUL status bar on focus
Last modified: 2008-11-12 20:45:32 UTC
Please describe the problem: When a <statusbarpanel> XUL element is focusable and Orca reaches it, it doesn't speak its contents. Steps to reproduce: 1. Fetch an example XUL file from http://www.freebsoft.org/~pdm/test9.xul . 2. Display it in Firefox by starting Firefox as `firefox --chrome test9.xul'. 3. Press the TAB key three times. Actual results: Only "general text" and "another text" get spoken, "status bar text" is not spoken. Expected results: "status bar text" is spoken when the statusbarpanel gets focus. Does this happen every time? Yes. Other information:
This appears as though it might be a Firefox/Gecko problem. Neither Orca nor Accerciser seem to get any events when one tabs from the "general text" area to the "status bar text" area. I'm CC'ing Aaron on this bug as well -- this definitely seems like it might be a Gecko/Firefox bug. Aaron, test document looks like the following: <?xml version="1.0"?> <?xml-stylesheet href="chrome://global/skin/" type="text/css"?> <window id="test-window" xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" xmlns:html="http://www.w3.org/1999/xhtml"> <description style="-moz-user-focus: normal">general text</description> <statusbar> <statusbarpanel label="status bar text" style="-moz-user-focus: normal"/> </statusbar> <description style="-moz-user-focus: normal">another text</description> </window> I think the status bar be emitting focus events when you tab to it. Does it do the right thing on Windows?
I just tried this in both Firefox 3.0.3 and Firefox 3.1b2pre and both times we spoke and brailled the "status bar text." Apparently it's claiming to be of ROLE_PUSH_BUTTON, but that is not an Orca bug. :-) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ LOCUS OF FOCUS: app='Firefox' name='status bar text' role='push button' event='focus:' GENERATOR: _getDefaultBrailleRegions obj = role = statusbar GENERATOR: _getBrailleRegionsForFrame obj = role = frame Finding top-level object for source.name= GENERATOR: _getDefaultBrailleRegions obj = Firefox role = application GENERATOR: _getBrailleRegionsForPushButton obj = status bar text role = push button BRAILLE LINE: 'Firefox Application Frame StatusBar status bar text Button' VISIBLE: 'status bar text Button', cursor=1 default.findCommonAncestor... ...default.findCommonAncestor GENERATOR: _getDefaultSpeech obj = status bar text role = push button already_focused = False utterances: (status bar text) (button) GENERATOR: _getSpeechForPushButton obj = status bar text role = push button already_focused = False utterances: (status bar text) (button) SPEECH OUTPUT: '' SPEECH OUTPUT: 'status bar text button' ^^^^^ PROCESS OBJECT EVENT focus: ^^^^^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Based on this, I believe this bug is FIXED. Closing as NOTGNOME. If there's an issue remaining which I'm missing, please feel free to reopen. Thanks!