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 676832 - Give each full screen window its own special workspace
Give each full screen window its own special workspace
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-05-25 18:00 UTC by semente
Modified: 2021-07-05 14:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description semente 2012-05-25 18:00:29 UTC
In OS X when you put the window as full screen (not maximized!), it creates a new special workspace and the panel in top becomes auto-hidden (when you hover the mouse it appears), also, and more important, any popup windows or any app that you load when inside this workspace, it moves you out to the origin workspace and opens these windows there, so only the full-screen window stays in the full-screen workspace and no other window appears at front or back of the full-screen window.

Follows a video explanation (unfortunately does not show all features): https://www.youtube.com/watch?v=GGVHjVH-NAc
Comment 1 Allan Day 2013-08-28 23:51:47 UTC
We've certainly wondered about this in the past, but I can't quite remember the specifics of what was discussed. CC'ing a few other designer types.
Comment 2 Mark Blakeney 2013-11-22 01:28:22 UTC
I use and love GNOME Shell but also use OS X and think this feature is great and would work well with GNOME Shell dynamic workspaces. I don't think it necessary to hide the top bar. Just auto-create a new workspace for the newly full screen window. If you think about it, anybody who sets a app/window full screen on top of other windows is implicitly wanting another workspace.

This should at least be an simple extension for an experienced GNOME dev?!
Comment 3 Jakub Steiner 2013-11-22 14:48:23 UTC
I would favor making fullscreen explicit (user driven) action that puts the application in a separate workspace. Many applications use fullscreen to essentially get rid of window decorations. That's not what fullscreen should be about. It's about toning down the lights and putting you in a theatre seat. No light, no controls/chrome*.

There are details to work out such as how the application is supposed to treat secondary displays.

This might be a duplicate of bug #705177

* on demand.
Comment 4 wyivgc 2014-12-30 03:44:56 UTC
Think of it as getting the people who talk on the phone during the movie out of the theatre, to go with your analogy.

With all due respect, but depending on your screen resolution, size and aspect ratio, the top bar uses up to 5% of the height of the display for what is essentially a glorified clock, as the shell comes out when you merely hover over the left corner with the mouse, the overlay on the right could do the same and the menu has its own button in the window.

It's fine for a collection of small windows, but not so much for a maximized window where it is a severe waste of screen estate.
Comment 5 Mark Blakeney 2017-08-08 04:51:13 UTC
For anybody who comes along looking for this function, there is an extension that provides it (nearly). See https://extensions.gnome.org/extension/1181/maximize-to-workspace/
Comment 6 GNOME Infrastructure Team 2021-07-05 14:46:45 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.