[xmonad] Issue 605 in xmonad: Tearing out a chrome or chromium tab with the mouse becomes tiled when it should be floating

[c***@google.com]

Updates:
Owner: ***@gmail.com

Comment #1 on issue 605 by ***@gmail.com: Tearing out a chrome or
chromium tab with the mouse becomes tiled when it should be floating
https://code.google.com/p/xmonad/issues/detail?id=605

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.

[c***@google.com]

Comment #2 on issue 605 by ***@gmail.com: Tearing out a chrome or
chromium tab with the mouse becomes tiled when it should be floating
https://code.google.com/p/xmonad/issues/detail?id=605

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.

[c***@google.com]

Comment #3 on issue 605 by ***@gmail.com: Tearing out a chrome or
chromium tab with the mouse becomes tiled when it should be floating
https://code.google.com/p/xmonad/issues/detail?id=605

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. :/