Bug 226483

Summary:	Drag'n'Drop not working with window tabs
Product:	[Plasma] kwin	Reporter:	Szakál Dániel <nantocsem>
Component:	window-tabbing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Szakál Dániel 2010-02-12 09:12:53 UTC

Version:           unknown (using 4.4.00 (KDE 4.4.0), Arch Linux)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.32-ARCH

I grouped 2 dolphin windows to a tabbed window. Surprisingly I had to untab them, because I couldn't drag and drop a file to the other, like they were basic windows.

Comment 1 Martin Flöser 2012-03-15 08:39:30 UTC

thinking aloud: what would happen if we switch the tabs if hovered during a d'n'd event? That probably would require support by the window decoration. Would the world collapse if we do that (e.g. Qt crashing applications)?

Comment 2 Thomas Lübking 2012-03-15 12:31:26 UTC

Unless the Qt bug meanwhile got fixed: "likely"
The other tab, being the DnD source, gets unmapped and Qt DnD (used to?) crash on that.
Another issue is the unreliable way of DnD implementation in X11, see bug #136856

The reason for this is that during DnD the pointer is grabbed and the client instead sends some client messages. Well, "message" on crossing for Qt that is, not on moves. Therefore the timeout calculation in the electric border fails. Dragging from ... other toolkits ... however works fully reliably here.
As a consequence we'd have tow switch tabs _immediately_ on DnD encounters, what would be rather nasty, i assume (or go for poling whether the pointer is grabbed and still there...)

Sidenote:
Dolphin btw. supports client internal tabbing which also and oc. supports DnD across tabs in the

Comment 3 Martin Flöser 2016-08-29 06:45:26 UTC

Unfortunately the rework in decorations in KWin 5 resulted in the window tabbing feature to be lost. We still want to bring this feature back, but after several versions it still hasn't emerged yet. Given that I think it is time to adjust the status of this bug report. The new implementation would be different anyway and it's questionable whether this report would still apply to it.