Detaching tabs and opening separated windows of Falkon is possible. I think the function to attaching tabs to browser's separated windows is basic enough option to considering it as a bug when it's missing. STEPS TO REPRODUCE 1. Open two separated Falkon windows 2. Open several tabs in each window 3. Try to move one tab from one window to the other. OBSERVED RESULT There is a sign appearing as if given tab could be placed on given window however it's still detached when you release it. EXPECTED RESULT Transferred tab placed among tabs of given window. SOFTWARE/OS VERSIONS Application version 3.0.1 KDE neon 5.15 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0.46-generic
I can't reproduce it, works correctly for me.
That's all, no further question, anything? Then I get used to this bug too and close this report frightfully quickly? Sorry, I mean it's quite interesting it works for you with the same circumstances since this is happening on both of my installation, I mean separated desktop PCs with KDE neon. https://drive.google.com/open?id=1wYUkDpSrkloPKLvtwyBZAgnlaumIMnKR
I'm not really sure what might be the issue. Can you please try with different window manager? Also, do you use Wayland? If so, please try with X11.
Created attachment 118724 [details] attempt LD_DEBUG for falkon with tab transferring issue (In reply to comment #3) SDDM with X11. It's KDE neon so I just did run away from gdm3 quikcly, I don't really want to deal with usable gnome environment setup becasue KDE neon sources are very edgy. Sorry I didn't recorded the very same issue there however I assure you it is also happening on gdm3 in the very same way. Sorry for the long video but I tried to point out that the browser is acepting tabs only after you touched the right or left edge of the tab line while you hold given tab with your mouse. Also I tried to create a backtrace, I don't know if any of this info would be helpful enough so I understand if more info should be provided. Le me know whenever you guys have time for this to proceed, I mean no rush. I also thought it can be caused by something else for example some windows management misbehaving however I already tried to turn off compositor and the issue presists without desktop effects too. https://drive.google.com/open?id=19tiLld_ubeq8ReaAI5XcvQXv39bSZH64
From the attachment I can see that you actually *are* using Wayland, so this might explain why it works for me. I can see from the video that it will only work when you first drag it onto desktop which "accepts" the drop, while Falkon window will not accept it.
Please try locking Plasma widgets: right click on desktop -> lock widgets.
Now I feel rebuked lol. I'm not lying and I'm not that stupid I won't know where am I login to neither. As far as I know, fundamentally and systemwide I use Xorg believe it or not. Good to hear some info were relevant from my attachment however I don't think the system uses Wayland in a significant way. I mean I also checked just now and yes there are Wayland related signs and I don't know how KDE neon works with Xorg exactly but I'm sure I can't even login to my system with Plasma Wayland if that's what you contend here. I login with basic Plasma what uses Xorg for sure. Why is it so sure Falkon is sick about any part of Wayland by the way? Please believe me this is my current output for this: loginctl show-session 3 -p Type Type=x11 Also no, it's not accepting after I drop it to desktop or whatever you mentioning. Please try to understand what I wrote and check the 2nd video, again, the end of the 2nd video more carefuly if you didn't see what I'm talking about. The only and the only case when falkon is accepting detached tab on this system when I touch the edge of Falkon's tab line with the cursor while I hold given tab to place. I don't know what other wording should I use, please check the 2nd video ending. Widgets lock didn't solve it. I won't expecting here anything, it's a simple bug report because for me, it seems a Falkon bug very much. Maybe it'll solved by you or by time cause this issue can be relevant to complex qt or any other stuff what Falkon uses. Firefox, Crhomium, Vivaldi works related to this altough they're a very different kind of browsers as it's obvious. Let me know if I should provide any other info or try out something else, thanks.
Otherwise no way you try this out on and actual KDE neon? Interesting to see KDE bugs won't be tested on KDE neon most of the time. Obviosuly I understand as it's not that resilient OS and just not worth the headache.
Unfortunately it's still issue. (It's Falkon 3.1)
Ofcourse it still, since you've reported it on the wrong place...
(In reply to The_assassin from comment #10) ???... Life is easier without unfinished stuff mostly. What are you talking about, this plase is worthless or it's something else lets say kwin issue? Anyways, no need to answer, I'm sure it's one of the most proper place to report this..... I'm here if users feedback worth something, otherwise there is always an other stuff to use as a tool. Probably I'd forgot fill out essential parts of my comments with .... though, espesially here.