GNOME Bugzilla – Bug 586078
Firefox speech output appears to be largely not working
Last modified: 2009-06-17 12:56:49 UTC
Please describe the problem: When visiting www.google.com.au orca doesn’t read most of the text on the page. When using orca plus tab I’m moved to the next form element but it is not spoken. This is not specific to google that is just one example. Now perhaps it’s something in my setup, I’m running orca from trunk with an otherwise standard Ubuntu Intrepid installation, no at-spi updates to 2.27 etc. I found the offending commit by doing a git bisect starting from the 1st june. I asked on the orca list if anyone else is seeing similar issues and Attila reported seeing the same problem. The git commit is: commit 1bfd7f20a455cb4dde944fc588a9eb0a8f71c76c Author: Willie Walker <william.walker@sun.com> Date: Sat Jun 13 08:47:35 2009 -0400 Add pauses before mnemonics (bgo#585417) Steps to reproduce: 1. visit www.google.com.au 2. use the up and down arrows to attempt to naviaate the page. 3. very little text is spoken, some of the links, not the buttons etc. 4. Use the arrow keys or control arrows to navigate by word. Text is spoken correctly when this is done. Actual results: expected Text is not spoken. Expected results: Correct text to be read out when navigating line by line or field by field. Does this happen every time? yes. Other information:
I confirm this problem with Ubuntu Jaunty and latest Orca release. I think this problem not produce you quoted commit, next comment I send full debug.out and the traceback message. The structural navigation.py file producing the traceback messages.
Created attachment 136800 [details] This full debug.out demonstrate Bart problem. Befre I analyze the debug.out file, I reproduce Bart described problem with following steps: 1. Locate Firefox with www.google.com 2. Press Orca+Tab key, the caret jumps the "Google search" button (google kereséz button if you would like search the debug.out in hungarian), but Orca does'nt spoken this button. I don't know in braille displays displayes the next or prewious form fields when the users using Shift+Orca+Tab or Orca+Tab key combination, because I have'nt got a braille display. When I analyze the debug.out file, I see following traceback messages: Traceback (most recent call last):
+ Trace 216042
consumed = self.function(script, inputEvent)
self.structuralNavigation.goObject(self, True)
structuralNavigationObject.present(obj, arg)
self._presentObject(obj, characterOffset)
self._script.speakContents(contents)
clumped = self.clumpUtterances(utterances)
clumped[-1][0] += " " + string
Attila
Created attachment 136801 [details] Prewious comment I send wrong debug.out file, this is the good debug.out file. Sorry, prewious comment I send wrong debug.out file. The traceback message is true, but second debug.out file show this message right.
*** Bug 586080 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 585870 ***