Bug 433960 - Cannot detach Chrome tab when draging to new window
Summary: Cannot detach Chrome tab when draging to new window
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.21.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-04 15:54 UTC by Armando Ota
Modified: 2021-03-04 19:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
video of draging tab into new window (3.57 MB, video/x-matroska)
2021-03-04 15:54 UTC, Armando Ota 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Armando Ota 2021-03-04 15:54:45 UTC 
Created attachment 136372 [details]
video of draging tab into new window

SUMMARY
I drag chrome tab out of current chrome window tab row to create a new chrome window. After I realease my mouse button, the release does not happen and as I move mouse around my newly created window with chrome tab follows my mouse. If my move my mouse to original chrome window tab row, it attaches it back. If i press space key when outside of the original chrome window, the new window is released and I get new window with my dragged chrome tab in it.

STEPS TO REPRODUCE
1. Open Chrome
2. Open 3 tabs in chrome 
3. Drag one tab out of current chrome tab row to create new chrome window with dragged tab

OBSERVED RESULT
after releasing mouse button (to end drag) window is not released and follows mouse cursor.

EXPECTED RESULT
Drag should stop and new window with dragged chrome tab is created.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-66-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz
Memory: 31.3 GiB of RAM
Graphics Processor: GeForce GTX 1080 Ti/PCIe/SSE2

ADDITIONAL INFORMATION
attacking video
Comment 1 Nate Graham 2021-03-04 16:57:45 UTC 
KWin doesn't handle mouse input at all on X11, so this would be a bug in Chrome itself.
Comment 2 Armando Ota 2021-03-04 17:04:13 UTC 
who handles drag event then ? Google chrome ?
Comment 3 Nate Graham 2021-03-04 17:28:22 UTC 
Chrome or the X11 server.
Comment 4 Armando Ota 2021-03-04 18:44:21 UTC 
thank you for explanation ... you might as well close this issue then
Comment 5 Nate Graham 2021-03-04 19:34:28 UTC 
I have. :)