SUMMARY In KDE, you can drag a window to the top of the screen in order to quickly maximize the window. However, using a top panel can disrupt this shortcut for certain apps, the most notable being Firefox; if you try to drag a tab out of Firefox and drag it to the top of the screen, it does not work because it tries to interact with the top panel instead. A user could avoid this issue by aiming the cursor below the top panel, but this is a disruption to muscle memory. YouTube video demonstrating the issue: https://youtu.be/lDNacyFONzc STEPS TO REPRODUCE 1. Add a top panel to your desktop (referred to as an Application Menu Bar) 2. Open Firefox and have two tabs open 3. Drag one of the tabs to the top of the screen where the top bar resides OBSERVED RESULT The cursor displays a little plus icon over the document icons. The widgets in the top panel may shuffle a bit. When letting go of left-click, nothing happens. EXPECTED RESULT I would expect for the Firefox tab to open in a new, maximized window. SOFTWARE/OS VERSIONS Distro: Arch Linux Linux version: 5.14.14 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2
X11 or Wayland?
It definitely occurs in X11, and I'm fairly sure it occurs on Wayland as well.
> I would expect for the Firefox tab to open in a new, maximized window. Why are you sure you can expect that? What are you dragging is not a window type, it is a tab. And if you drop it, outside of any firefox window, the window will be created with that tab. After that you can work with that window as usual. Also, I run firefox with MOZ_ENABLE_WAYLAND=1, and when I drop its tab outside of firefox window (even when hitting top edge), the new firefox window appears with that tab (the size corresponds parent firefox window, not exactly maximized). Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Graphics Platform: Wayland Firefox: 117.0
I think this is just a side effect of Bug 436601. KWin doesn't know that the tab is actually a window so it can't interpret the drag as the intent to both tear off the tab and maximize it. *** This bug has been marked as a duplicate of bug 436601 ***