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 701217 - Classic: [RFE] Classic mode should have "Workspaces only on primary monitor" set to False by default
Classic: [RFE] Classic mode should have "Workspaces only on primary monitor" ...
Status: RESOLVED WONTFIX
Product: gnome-shell
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on: 701717
Blocks:
 
 
Reported: 2013-05-29 18:40 UTC by Stephen Gallagher
Modified: 2015-02-27 16:01 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
classic: Don't default to workspaces-only-on-primary (1.49 KB, patch)
2013-06-06 22:28 UTC, Florian Müllner 		none Details | Review

Description Stephen Gallagher 2013-05-29 18:40:16 UTC 
As I understand it, the goal of Classic mode is to provide a classic GNOME 2 look-and-feel. To that end, it seems most beneficial to have the default behavior of workspaces to be that they work on all monitors. For users with multiple monitors (a growing community!), having the workspace switch only on the primary monitor by default feels like a bug.
Comment 1 Vít Ondruch 2013-06-04 14:56:59 UTC 
This is probably duplicate of bug 645581.
Comment 2 Stephen Gallagher 2013-06-04 16:43:14 UTC 
I disagree. I'm not recommending this behavior for the standard GNOME Shell case, but I do strongly advise that it should be the behavior when operating in GNOME Classic mode.

I think these two tickets should be tracked separately.
Comment 3 Florian Müllner 2013-06-06 22:28:19 UTC 
Created attachment 246195 [details] [review]
classic: Don't default to workspaces-only-on-primary

The GNOME 3 default prioritizes the use case of connecting casually
connecting external displays like projectors or TVs over the "classic"
multimonitor case. While this makes sense for the default session,
users tend to expect the old behavior in classic mode.


Patch on top of bug 701717 in case we want to go with this ...
Comment 4 William Jon McCann 2013-06-06 23:25:34 UTC 
The reasons we don't put workspaces on secondary displays such as projectors is independent of the reasons for classic mode. This sounds like a dup of bug 645581 to me.
Comment 5 Florian Müllner 2015-02-27 16:01:42 UTC 
Closing as of comment #4 (I don't think dup'ing makes much sense - the setting exists nowadays, this bug is just about whether its default should be different for classic and normal sessions ...)