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 709034 - Switching to window and then scrolling hides window
Switching to window and then scrolling hides window
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: overview
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 720484 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-09-29 12:10 UTC by Remco
Modified: 2013-12-15 12:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
overview: Add cover pane directly to overviewGroup (1.25 KB, patch)
2013-09-29 21:40 UTC, Florian Müllner
committed Details | Review

Description Remco 2013-09-29 12:10:56 UTC
If you are in overview mode and you switch to a scrollable window, then you have to wait until the animation is finished before actually starting to scroll. If the animation is not finished, you're technically still in overview mode, where the scroll action moves you to the next workspace. In the most common case, you'll end up moving to an empty workspace, effectively hiding all windows.
Comment 1 Florian Müllner 2013-09-29 21:40:28 UTC
Created attachment 256040 [details] [review]
overview: Add cover pane directly to overviewGroup

The cover pane is used to block events during transitions, but as
workspaces don't share the same container as other overview elements,
they are currently excempt from the event blocking.
Move the cover pane to the top-level overview container instead.
Comment 2 drago01 2013-10-01 12:37:22 UTC
Review of attachment 256040 [details] [review]:

OK.
Comment 3 Florian Müllner 2013-10-01 15:18:02 UTC
Attachment 256040 [details] pushed as 46edc05 - overview: Add cover pane directly to overviewGroup
Comment 4 Florian Müllner 2013-12-15 12:17:01 UTC
*** Bug 720484 has been marked as a duplicate of this bug. ***