GNOME Bugzilla – Bug 629401
When I search anything with www.google.com and send search text, unable to navigate structural navigation keys before I press Tab key
Last modified: 2011-01-10 00:04:37 UTC
Created attachment 170064 [details] This problem demonstrating possible why happening the described problem Dear Developers, When I using www.google.com webpage, write a search text and press Enter key, unable to navigate structural navigation keys before I not move the caret focus for example the Tab key. Unfortunately this problem is always reproducable, I don't no possible fix this problem or not. The reproducation verification is very easy: 1. Launch Firefox web browser, and open www.google.com webpage. 2. Write the search text box for example Orca screen reader text, and press Enter key. The results are displayed. 3. Try navigate for example headings with h or Shift+h key. Unfortunately nothing happening, Orca doesn't jump next or prewious headings. When you press Tab key one time, structural navigation keys again working, possible jump the search results with h or Shift+H keys. This bug is present both Orca 2.30.2 and latest Orca git master version. I maked a debug.out file, and see following trace back error message with latest git master version of Orca, I don't no this is help you identifiing why happening this problem: Traceback (most recent call last):
+ Trace 223663
s.processObjectEvent(event)
self.listeners[key](event)
self.liveMngr.handleEvent(event)
message = self._getMessage(event)
self._script.utilities.expandEOCs(event.any_data)
childText = self.expandEOCs(child)
child = obj[i + childOffset]
raise IndexError IndexError
I attached recorded debug.out file. Attila
I can't reproduce this in firefox 4 beta's, I notice that the default focused heading is the first search result which is a little interesting, but if the first thing I type on a page of results is 'h' I get to a heading that is a search result, and h and shift h keep working
what version of firefox are you using?
Trevor, I using Firefox 3.6.13 and my primary system is Ubuntu Lucid. But if need I have got a Natty testing system with awailable Firefox 4.0 beta8 I think. Attila
Since this issue seems to be fixed in firefox I'm considering this closed as not gnome since it was fixed in firefox. If you can reproduce in firefox nightly builds please reopen