Bug 503623

Summary:	Dragging chromium tabs behaves weirdly
Product:	[Plasma] kwin	Reporter:	Friedrich <friedrich.public.2001>
Component:	Wayland drag-and-drop	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	john.kizer, strong.drum0546
Priority:	NOR
Version First Reported In:	6.3.4
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Friedrich 2025-05-01 16:36:18 UTC

SUMMARY
There are three problems here:

1. When dragging a chromium tab (not window!) the dragged tab will not be focused until it's dropped. (So basically if another window is focused and you start dragging a tab from a chromium window that isn't focused, then that dragged tab will be dragging below the focused window.)

2. Sometimes chromium tabs merge with a window that is covered behind other windows. Unfortunately this only happens sometimes and I haven't yet found a way to reliably reproduce this.

3. When a chromium window is tiled to the left/right half of the screen and you start dragging a tab from it, then that dragged tab will remain glued to the top and bottom of the screen during the dragging.


EXPECTED RESULT
1. The dragged tab should become focused with the begin of the drag.

2. Tabs shouldn't be able to merge with windows that are covered behind other windows.

3. The tab dragging experience should feel like the tab is sticking to the cursor.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE 

ADDITIONAL INFORMATION

Comment 1 Lenzoid 2025-05-01 23:06:02 UTC

1. + 2. : cannot reproduce on git-master. Have never seen that in any case. It could be that it will be fixed in next major release or it is an issue in Fedora. It would be interesting if you can reproduce it on something like the Neon unstable live image. It contains the most recent KDE version. If you want to check out what the team has been working on this could be interesting for you (lots of awesome improvements imo).

3: not entirely sure what you mean, but it sounds like a Chromium design choice. 

Maybe enabling the Wayland display system in Chrome improves your situation? Setting chrome://flags > Preferred Ozone platform to "Auto". I am using it but it is in beta and has its issues.

Operating System: Arch Linux 
KDE Plasma Version: 6.3.80
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X3D 8-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 2070 SUPER
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B85
System Version: 1.0
GPU driver Version: nvidia-open-dkms 570.144-1

PS: Just to be aware of it for the future: it is generally not recommend putting different issues into one ticket as it can become confusing quickly.

Comment 2 John Kizer 2025-05-05 05:21:34 UTC

Thanks for the bug report! Unfortunately it reports multiple distinct issues, which will make it not actionable. See https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more explanation.

Can I ask you to submit a new bug report for each specific issue? Thanks again!