Launchpad has imported 8 comments from the remote bug at http://bugs.opencompositing.org/show_bug.cgi?id=1027.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-08-13T17:25:13+00:00 William-walker-z wrote: a11y == accessibility I work on the Orca screen reader project (http://live.gnome.org/Orca). As we have done with metacity, we are trying to provide compelling presentation as the user presses Alt+Tab to navigate between windows on the desktop using Compiz. As seen in http://bugzilla.gnome.org/show_bug.cgi?id=466841#c8, we are noticing some really strange behavior when the user releases the Tab key after pressing Alt+Tab. In particular, given the scenario where the user Alt+Tab's from window A to window B, we see the following sequence of AT-SPI events: (Alt+Tab initially pressed here) A: window:deactivate (Alt+Tab released here) A: window-activate B: window:activate A: window:deactivate This overlapping of window activation events is really quite strange (it says two windows are active at once). Ideally we'd just get this: (Alt+Tab initially pressed here) A: window:deactivate (Alt+Tab released here) B: window:activate Thanks! Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/0 ------------------------------------------------------------------------ On 2008-08-13T17:44:18+00:00 William-walker-z wrote: In testing more with compiz 0.7.7 on the latest Ubuntu Intrepid, I'm also seeing this event ordering when Alt+Tab'ing from A to B: (Alt+Tab initially pressed here) A: window:deactivate (Alt+Tab released here) B: window-activate A: window:activate A: window:deactivate Again, ideally we'd just get this: (Alt+Tab initially pressed here) A: window:deactivate (Alt+Tab released here) B: window:activate Thanks! Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/1 ------------------------------------------------------------------------ On 2008-08-13T18:44:03+00:00 Maniac-y wrote: What exactly triggers those window:activate and window:deactivate events? I mean, what X event is the root of those? Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/2 ------------------------------------------------------------------------ On 2008-08-13T20:40:57+00:00 William-walker-z wrote: (In reply to comment #2) > What exactly triggers those window:activate and window:deactivate events? I > mean, what X event is the root of those? I'm not sure. I'm guessing FocusIn and FocusOut. This might be ultimately done by moveInputFocusToWindow in http://cgit.freedesktop.org/xorg/app/compiz/tree/src/window.c, which is called by activateWindow and hideWindow in the same module. But don't let the above trick you into thinking I know anything about compiz. :-) I don't. I was just scouring sources. Speaking of scouring, I did a little more, but this is just naive scouring: on the GTK+ side, gtk+/gdk/x11/gdkevents-x11.c listens for FocusIn/FocusOut events and generates a GDK_FOCUS_EVENT. This is processed by gtk+/gdk/gdkevents.c, and things end up getting bubbled up to gtk+, which turns them into 'focus-in-event' and 'focus-out-event' events. The AT-SPI GAIL module picks these up and issues "window:activate" and "window:deactivate" events accordingly. Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/3 ------------------------------------------------------------------------ On 2008-08-14T06:12:05+00:00 Maniac-y wrote: Ok, it most likely _is_ FocusIn / FocusOut and also most likely is grab related. Here are the FocusIn and FocusOut events happening on a switch gnome- terminal -> gcalctool: focusOut 119537694 (gnome-terminal), mode 1, detail 1 focusIn 422 (), mode 1, detail 2 focusIn 119537694 (gnome-terminal), mode 1, detail 5 ---> switcher plugin initiated focusOut 119537694 (gnome-terminal), mode 1, detail 5 focusOut 422 (), mode 1, detail 2 focusIn 146800729 ((null)), mode 1, detail 0 moveInputFocusToWindow 136314883 (galculator) focusOut 146800729 ((null)), mode 2, detail 3 focusIn 119537694 (gnome-terminal), mode 2, detail 4 focusOut 119537694 (gnome-terminal), mode 0, detail 4 focusIn 136314883 (galculator), mode 0, detail 3 focusOut 136314883 (galculator), mode 0, detail 2 The first three are the keyboard grab becoming active due to Alt+Tab being pressed. The next three are the pointer grab becoming active through switcher. The last 5 happen after releasing Alt+Tab and thus releasing both grabs and moving the focus. The printed data are the window, mode and detail members of the XFocusChangeEvent struct. I don't have the time to do a deeper analysis at this moment (will do as soon as I have some time), but if you have some X/Gdk expert at hand, that'd be helpful ;) Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/4 ------------------------------------------------------------------------ On 2008-08-14T14:47:06+00:00 William-walker-z wrote: (In reply to comment #4) > Ok, it most likely _is_ FocusIn / FocusOut and also most likely is grab > related. Nice analysis. Thanks! How did you do it? It would be really interesting to analyze the events from metacity in the same way. As we see in http://bugzilla.gnome.org/show_bug.cgi?id=466841#c9, it seems to be able to do the right thing. So, hopefully it will just be a matter of trying to duplicate that. Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/5 ------------------------------------------------------------------------ On 2008-08-14T15:09:57+00:00 Maniac-y wrote: (In reply to comment #5) > (In reply to comment #4) > > Ok, it most likely _is_ FocusIn / FocusOut and also most likely is grab > > related. > > Nice analysis. Thanks! How did you do it? I added debug output to the FocusIn / FocusOut event handlers of Compiz. As it selects for FocusChange events on all toplevel windows anyway, all events are printed. Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/6 ------------------------------------------------------------------------ On 2009-05-17T03:15:44+00:00 Joanmarie Diggs wrote: Ping. :-) As more and more distros are shipping with Compiz as the default window manager, this bug is impacting more and more users who are blind. Reply at: https://bugs.launchpad.net/compiz/+bug/801582/comments/7 ** Changed in: compiz Status: Unknown => Confirmed ** Changed in: compiz Importance: Unknown => Medium ** Bug watch added: GNOME Bug Tracker #466841 https://bugzilla.gnome.org/show_bug.cgi?id=466841 ** Changed in: gnome-orca Status: Unknown => Confirmed ** Changed in: gnome-orca Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/801582 Title: orca: alt-tabbing between windows - descriptions become interleaved confusingly To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/801582/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
