GNOME Bugzilla – Bug 766238
"Hide Window" is awkward to use
Last modified: 2021-07-05 14:28:17 UTC
Yes, there's no minimize button in the chrome, but the keybinding is available, and using it is frustrating. Say my application MRU, as visualized in alt-tab, is: [firefox] [terminal] [rhythmbox] And that rhythmbox' window is minimized. I switch back to it to skip to the next song, then hit super-h to hide it. My MRU now looks like: [firefox] [rhythmbox] [terminal] Which means my next alt-tab will switch me back to the rhythmbox I just dismissed as uninteresting. On OSX, by contrast, cmd-h will not only withdraw the application's windows but move it to the end of the MRU. OSX has two actions here: cmd-m to minimize window, and cmd-h to hide application. Minimizing all of an app's windows does not switch app focus; the titlebar remains that of the application. Hiding an application remembers which windows were minimized and which were not; restoring restores that state. Personally I'm not a fan of "app in foreground with no windows" as a UI state. So if I were to bring the min/hide distinction to shell, I would expect min and hide of the last visible window of an app to be identical: the window is withdrawn, and the app moved to the end of the MRU.
Created attachment 327610 [details] [review] app: Consider minimized windows for app comparisons We used to take window visibility into account when comparing apps until commit 1dfc38d078, following changes in the window switcher due to auto-minimization. However auto-minimization was abolished and the window switcher changes reverted, so it makes sense again to sort apps without non-minimized windows last again.
Review of attachment 327610 [details] [review]: looks good
Comment on attachment 327610 [details] [review] app: Consider minimized windows for app comparisons Attachment 327610 [details] pushed as 84da49c - app: Consider minimized windows for app comparisons Not sure we want to consider app-minimization (in addition to the existing window-minimization), but keeping the bug open for now.
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.