After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 671998 - Keyboard navigation in app menu on new workspace
Keyboard navigation in app menu on new workspace
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
3.3.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-03-13 15:38 UTC by Shaun McCance
Modified: 2012-03-17 00:14 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
AppMenuButton: Don't set the actor reactive if it's not really visible (1.04 KB, patch)
2012-03-13 18:20 UTC, Rui Matos 		committed Details | Review

Description Shaun McCance 2012-03-13 15:38:42 UTC 
* Open any application
* Switch to a new workspace by mousing to the activities overview, clicking the empty workspace on the right, then clicking the desktop to exit the overview. This bug can only be triggered when mousing to a new workspace. It does not happen with Ctrl+Alt+Down.
* Press Ctrl+Alt+Tab to give keyboard focus to the top bar.
* Press right once. Notice that nothing on the top bar appears to have focus.
* Press Enter. Observe a menu appear out of nowhere.
* Navigate to Quit and press Enter. Your last-focused app on some other workspace goes away.
Comment 1 Rui Matos 2012-03-13 18:20:53 UTC 
Created attachment 209635 [details] [review]
AppMenuButton: Don't set the actor reactive if it's not really visible

Reactive means that the actor is reachable from keyboard
navigation. If the target isn't current that means we are not tweening
the actor to be visible so we can't set it reactive either.
Comment 2 Florian Müllner 2012-03-16 16:16:13 UTC 
Review of attachment 209635 [details] [review]:

Minor nit in the commit message: "... we can't set it reactive" - if we really couldn't, there would be no bug - I think "... we shouldn't set it reactive" makes more sense :-)
Comment 3 Rui Matos 2012-03-17 00:14:37 UTC 
Pushed with the suggested commit message change.

Attachment 209635 [details] pushed as 22e1abb - AppMenuButton: Don't set the actor reactive if it's not really visible