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 648140 - switch workspaces by scrolling on the background in the overview
switch workspaces by scrolling on the background in the overview
Status: RESOLVED DUPLICATE of bug 686639
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-18 18:01 UTC by Allison Karlitskaya (desrt)
Modified: 2013-05-15 21:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Allison Karlitskaya (desrt) 2011-04-18 18:01:00 UTC 
Seems like an obvious enough feature.

The only argument that I can think of against it is that some users might intend to zoom a window, but slightly miss the window and inadvertently change workspaces.
Comment 1 Florian Müllner 2011-04-18 19:36:11 UTC 
(In reply to comment #0)
> Seems like an obvious enough feature.

Yeah, I had an implementation at one point, but decided that it was better to leave it out ...

 
> The only argument that I can think of against it is that some users might
> intend to zoom a window, but slightly miss the window and inadvertently change
> workspaces.

The other way round is actually worse - you scroll the background to switch workspace, end up with the pointer on a window, so instead of scrolling further, a random window is zoomed in ... only speaking for me, but I found that behavior extremely annoying.
Comment 2 gnu.lu0 2013-04-24 20:58:35 UTC 
This feature made it into gnome 3.8, but it's barely useful with a touchpad with smooth scrolling. It's way too sensitive. Maybe it should behave like when holding the left mouse button on the background to move between workspaces
Comment 3 Florian Müllner 2013-05-15 21:33:18 UTC 

*** This bug has been marked as a duplicate of bug 686639 ***