Skip to content
This repository has been archived by the owner on Jun 16, 2024. It is now read-only.

[Bug]: Dragging a tab from chrome causes strange behaviour #105

Open
xtalax opened this issue Oct 12, 2021 · 4 comments
Open

[Bug]: Dragging a tab from chrome causes strange behaviour #105

xtalax opened this issue Oct 12, 2021 · 4 comments
Labels
bug Something isn't working needs more info The issue needs more information from the submitter side

Comments

@xtalax
Copy link

xtalax commented Oct 12, 2021

Summary

Dragging a Chrome tab out in to a new window has expected behaviour (50/50 split tiling) initially, but upon letting go the original window returns to its original size

Steps to Reproduce

Open chrome on its own on a virtual desktop, create a new tab, drag tab out to new window

Expected behavior

Windows remain tiled

Screenshots

No response

Bismuth version

most recent release, installed with wget command in readme

KDE Plasma version

5.22.5

The platform KWin is running on

X11

Additional context

No response

@xtalax xtalax added the bug Something isn't working label Oct 12, 2021
@xtalax
Copy link
Author

xtalax commented Oct 12, 2021

This also happens with VSCode, and resolves after moving a window to another virtual desktop and back, implying that the layout is not refreshed when creating a new window in this way. Refreshing the layout after a new window is created in any way may resolve this, and should be a quick fix

@gikari
Copy link
Member

gikari commented Oct 14, 2021

Do I understand correctly, that you want to drag the tab out of Chrome to the empty space on a desktop (or a browser content space), so that that tab creates a new window, that tiles alongside? Because I cannot reproduce: it works perfectly fine for me.

@gikari gikari added the needs more info The issue needs more information from the submitter side label Oct 14, 2021
@maxicarlos08
Copy link

I am having the same issue on Brave (which is based on chromium), it happens directly when I start dragging the tab, even if its only inside the window, this does not happen to Firefox.

VSCode is working fine for me.

@maxicarlos08
Copy link

Any updates on this from someone else? It seems to be fixed for me for while now

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working needs more info The issue needs more information from the submitter side
3 participants