search

codehenry / xmonad

Automatically exported from code.google.com/p/xmonad
0 stars 0 forks source link

Tearing out a chrome or chromium tab with the mouse becomes tiled when it should be floating #605

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Use the mouse to drag (tear) a chrome tab out of your chrome window.
2. Experience annoyance when everything moves to accomodate a newly tiled 
window.

What is the expected output? What do you see instead?
This new window should float until the drag stops. This used to be the behavior 
a year or two ago.

See the chrome issue over here 
https://code.google.com/p/chromium/issues/detail?id=447988.

Original issue reported on code.google.com by jeremyfl...@gmail.com on 26 May 2015 at 10:00

GoogleCodeExporter commented 8 years ago 
First I need to beef up DebugWindow and the upcoming ManageDebug so I can see 
if there is some way to identify the "ghost window" chrome creates and either 
float or doIgnore it, rather than tiling it and terminating the drag.

Original comment by allber...@gmail.com on 26 May 2015 at 10:03

GoogleCodeExporter commented 8 years ago 
I did so locally and found it's not being created. Also found 
https://code.google.com/p/chromium/issues/detail?id=416119 and it occurs in 
other tiling WMs as well. Asked there for more information from chromium devs.

Original comment by allber...@gmail.com on 28 May 2015 at 5:49

GoogleCodeExporter commented 8 years ago 
Interesting observation: at least with recent Chrome, it seems that if I drag 
slowly enough I can drag tabs even sloppily. I will briefly get a new window 
that gets tiled --- but as long as I keep dragging, when I reach the tab bar of 
the other Chrome window the temporary tiled window will go away and the tab 
will appear.

I suspect that xmonad reshuffling windows as focus changes can impact this 
pretty badly, though, such that everything gets confused and the tab just gets 
tiled because the target window got whisked away by the StackSet reshuffle. 
Sadly, this is another manifestation of bug 4 and the only fix is to ditch the 
StackSet entirely, breaking pretty much everything in the process. :/

Original comment by allber...@gmail.com on 6 Aug 2015 at 2:42