GNOME Bugzilla – Bug 385949
[blocked] Orca has traceback with Firefox 3.0 nightly when testing bookmarks.
Last modified: 2007-03-14 14:41:53 UTC
Testing Firefox 3.0 nightly build on Ubuntu Edgy. In particular testing bookmarks and got a traceback: Child at index 0 is not an Accessible Traceback (most recent call last):
+ Trace 94191
s.processObjectEvent(event)
self.listeners[key](event)
default.Script.onFocus(self, event)
orca.setLocusOfFocus(event, newFocus)
orca_state.locusOfFocus)
newLocusOfFocus)
self.updateBraille(newLocusOfFocus)
default.Script.updateBraille(self, obj, extraRegion)
result = self.brailleGenerator.getBrailleRegions(obj)
return braillegenerator.BrailleGenerator.getBrailleRegions(\
result = generator(obj)
if menu.name:
Full debug.out to be attached...
Created attachment 78382 [details] debug.out generated during test
Here's one way to reproduce the stacktrace: press Ctrl+D to bring up the "Add Bookmark" page. When the "Name:" entry field gets focus, Orca seems to issue the stack trace.
This appears to be an accessibility implementation bug in Firefox. In looking at the "NameL:" entry area, it is a combo box, but is doesn't provide any text or children (i.e., we cannot get to the text being displayed). I'll dig into this some more and log a bug if need be.
I'll be adding a patch to prevent the traceback, but there's still a looming Firefox bug that prevents access to the "Name:" field: https://bugzilla.mozilla.org/show_bug.cgi?id=363955. Marking this as blocked.
Created attachment 78436 [details] [review] Patch to prevent stack trace This patch prevents the stack trace, but access to the component in question (the "Name:" combobx in the "Add Bookmark" dialog) is broken due to an underlying Firefox accessibility implementation bug.
It looks like they recently fixed the issue with the Name: combo box. Coincidentally or otherwise, it seems that we now get an error from that dialog's Create In combo box. From this build: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a3pre) Gecko/20070211 Minefield/3.0a3pre I get this focus event and error in Orca: vvvvv PROCESS OBJECT EVENT focus: vvvvv OBJECT EVENT: focus: detail=(0,0) app.name='Minefield' name='Create in:' role='combo box' state='ENABLED EXPANDABLE FOCUSABLE FOCUSED HORIZONTAL OPAQUE SENSITIVE SHOWING VISIBLE' relations='LABELLED_BY' LOCUS OF FOCUS: app='Minefield' name='Create in:' role='combo box' event='focus:' GENERATOR: _getBrailleRegionsForDialog obj = Add Bookmark role = dialog GENERATOR: _getBrailleRegionsForAlert obj = Add Bookmark role = dialog GENERATOR: _getDefaultBrailleRegions obj = Add Bookmark role = dialog GENERATOR: _getDefaultBrailleRegions obj = Minefield role = application GENERATOR: Gecko._getBrailleRegionsForComboBox obj = Create in: role = combo box Traceback (most recent call last):
+ Trace 109894
self, obj, groupChildren)
regions.append(braille.Region(item.name))
Created attachment 82345 [details] [review] conservative patch to handle a recent change in FF3 This solves the problem in my previous comment.
I just tested the above patch on both Edgy and Feisty using versions of FF3 before their combo box change and after, examining both combo boxes in FF dialogs and those within web pages. Everything seems to check out okay. As per Will, the patch -- with additional comments added for better documentation -- has been committed. Will, now that we don't have tracebacks, and the Add Bookmark dialog is behaving properly, I think this bug can be closed.
Closing as FIXED. Thanks Joanie!