Sway: Can't move tabs under Chrome - XWayland if another XWayland application is open in another workspace

[fourstepper]

Please fill out the following:

• Sway Version: 1.4 and 1.5

• Distribution: Fedora 32 EDIT: and Fedora 33

• Description:

  • It is not possible to move tabs in the same window or from a new window to a different window if a different XWayland application is open at the same time in a different workspace. I used Spotify flatpak to tests this

Steps to reproduce:
1) Open Chrome (observe described functionality working normally)
2) Go to a different workspace, open Spotify (or other XWayland app)
3) Return the Chrome workspace and try to move a tab around.

For me after the above steps any movement on the tab creates a new window, from which the tab cannot be returned to the previous window via drag&drop

[Algram]

Having the exact same problem here.

Sway 1.5, nixos-unstable

I think it might be related to the latest Chrome update that introduced tab-groups. I tried disabling the tab-groups feature in Chrome but it does not solve the issue.

[kellpossible]

I can't move tabs around at all with chromium, trying to drag them just creates a new window, and also seems to induce lag. Seems to be associated with a recent chromium update.

[jsravn]

I also notice you can no longer drag items, such as in the bookmark manager. And can't drag/drop bookmark folders on the bookmark bar. I assume this is related to not being able to move tabs.

[roshal]

i experiencing the same problem with chromium under sway on archlinux

[jsravn]

Also can't drag items in the github project view! So it seems drag events are just not working? Possibly something to do w/ focus.

[efenex]

Same here with brave - no dragging/dropping in the browser at all for i.e. bookmarks, dragging tabs creates new windows and causes massive lag (that's probably a different issue)

[slyon]

Same here with Chrome 86 on Ubuntu 20.10 and sway 1.5

[moonbone]

seems to be fixed for me now on arch with:
chromium 86.0.4240.111-2
sway 1:1.5-1

Edited: well... actually there is some improvement, but some stuff still doesn't work as I expected it to. Mostly when in tabbed layout, or when chromium is open on several workspaces on the same output.
Seems like when several chromium instances share the cooridinates then the catching the floating tab can't be determined in advance.

[fourstepper]

I think I have managed to limit the problem only to other full screen applications under XWayland in a different workspace - I hope this information is of any use

sway v. 1.5
Fedora 33