Windows in several workspaces move themselves to be in one
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
New
|
Undecided
|
Unassigned |
Bug Description
This is a problem that's been around for a long while, but because of various window/workspace related bugs (e.g.: https:/
When a window is placed so that it touches two or more workspaces, when it is selected via the launcher or alt-tab and it's mostly on a different workspace, both the view *and the entire window* shifts to that workspace.
To reproduce:
1.) Open any application (not maximized).
2.) Place it so that most of the window is on an adjacent workspace.
3.) Click on the desktop or another application.
4.) Select the application via the launcher or alt-tab.
5.) The view is now shifted to the adjacent workspace, where the window has moved itself so that it resides there in its entirity.
Expected results:
I'm not actually sure what should happen... but see two options:
Option #1: When the launcher/alt-tab selects the window that is partially on the current workspace, the window does not move but the workspace shifts to whichever workspace the majority of the window is on.
Option #2: When the launcher/alt-tab selects the window that is partially on the current workspace, the window does not move, nor does the workspace if any part of the window is in it (if none of it is on the current workspace, it moves to the one where most of the window resides).
Option #1 seems to make the most sense, but there are some cases when it could cause inconsistencies. What if you maximize a window with only a little bit of it on the current workspace? Which workspace would it maximize on? What if a window is moved to the side but the user still wants to use it on the current workspace, even if less than half is on it? Maybe windows should just only ever be seen on one workspace.
Regardless, windows should not move unless the user moves them!
Thanks.
This is the exact same behavior I noticed in bug #1092323.
https:/ /bugs.launchpad .net/bugs/ 1092323
How about this option?
Option #3: When a window opens for the first time inside a workspace, the launcher "remembers" or associates that window with that workspace even if you move the majority of the window into another workspace. Until you move the entire window into another workspace, clicking on the window's launcher icon will always move back to the originating workspace.