GNOME Bugzilla – Bug 577705
When Orca starts doesn't get to the component with focus.
Last modified: 2010-08-16 15:29:27 UTC
Please describe the problem: When Orca starts and any application has focus, Orca doesn't get into the widget that currently has focus, the locus of focus get stuck at frame level. Steps to reproduce: 1. Open an application. E.G Gedit text editor. 2. Start or reaload Orca. 3. Use the command "where am I" to get detailed information or try to work with the currently focused application. E.G move the cursor or write some text. Actual results: Orca doesn't give information about the real widget with focus (in this case the text area of Gedit). Expected results: Orca should report the currently locus of focus is the text edit area of currently focused application. Does this happen every time? Yes Other information:
As a workaround, if you Alt+Tab away from gedit and then Alt+Tab back to it, do thing work as expected? I believe the problem is that Orca doesn't traverse down the hierarchy of the focused application to find the object with focus. This is done for performance reasons. As a potential solution, we could potentially put up a window that grabs focus and then destroy that window (e.g., something like a splash screen). With this, the window manager would give focus to the application window and we'd rely upon the application window to issue a focus event.
Planning spam. Sorry!
http://git.gnome.org/browse/orca/commit/?id=122195bf2f9905df05462857e0c7a3de3448f132
Maybe I have not understood correctly this bug but seems to me that it was not solved. If I am in gedit and I restart orca, orca stays mute when I scroll in the file using the arrows. I need to press alt+tab and press alt+tab again to restore things to normal state.
Thanks José. That's why we rely upon testing from you and the other users. Reopening.
So there are a couple of things going on here. Ale fixed the primary issue, namely if the Orca main window is not showing, the locusOfFocus is not getting set and Orca speaks nothing, like at all, until you Alt+Tab. What is happening now is that the Gedit frame is claiming focus. But the text widget which has focus is not claiming focus. If you get into the Gedit Find dialog and repeat your test, and then tab around the Find dialog, you should discover Orca speaks the items with focus -- because we're getting the expected focus: events. Likewise, I believe you'll find that you do not have to Alt+Tab out of Gedit. It should be sufficient to get into and out of Gedit's File menu. That, too, will cause Gedit to emit the correct focus: event. I'm not sure if there's something else we can do here to work around this Gedit (or Gtk+) bug, but Ale and I will look for it. Stay tuned!
Testing with gedit and gnome-terminal. After restart orca, if I activate menu pressing f10 and then press esc, things goes to normal state. No need to press alt+tab ana alt+tab again.
Yup, if widgets would give us the expected events, our jobs would be much easier. <smile> Ale, I consider this a separate bug. Let's reopen one for this new issue and re-close out this bug. Sorry and thanks!
New bug #627052 created. I close this bug.