Bugzilla – Bug 1216842
Firefox all tabs list issues on KDE Wayland - cannot move tabs in list
Last modified: 2024-02-02 03:13:13 UTC
Created attachment 870608 [details] Left side: list too short. Not working. Right side: List longer than screen, works. In KDE Wayland sessions, tabs in the all tabs list cannot be drag-and-dropped to move them. This is reproducible in openSUSE KDE Live DVD images including today's most recent one, so fully up to date and completely unmodified. eg https://mirror.2degrees.nz/opensuse/tumbleweed/iso/openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20231031-Media.iso Just boot it ina VM and observe this bug in action. You will need to log out of the default X11 session and then log into a KDE Wayland session, start firefox, create several tabs, opent he all tabs list, and try to drag and drop them. You will fail. I have tested this on 3 different bare metal machines as well as VMs. This does not occur in KDE X11 sessions, or in Wayland sessions on other DEs or distros. It is specific to openSUSE KDE Wayland. I keep trying to open this bug and it gets closed or moved off this project and gets no visibility, so if you're wondering why I'm creating it again, no, I'm not spamming, I'm un-breaking it the only way I can. I've found a way to prove it too, because I found a workaround. If you make the all tabs list longer than the screen, it starts to work. You can then close the superfluous tabs and it continues to work for that window only. Screenshot attached. This is screen-size-specific - if I do it on a 1440p monitor, the list must have more tabs than for the 1080p monitor. It has to reach the bottom of the screen, then it magically starts to work. Restarting firefox will reset this behaviour, it is not maintained with the session. In the screenshot you can see I have taken the browser and hit ctrl+t a bunch of times to create a list, one tab shorter than the length of the screen. At the moment of this screenshot I have clicked and dragged one of the tabs and it will not move. Note the lack of blue marker on the left. Then I hit ctrl+t one more time, to create an extra tab. Now the list is long enough to fill the screen, and it works as it should always do, and grab a tab, drag it, and I take the screenshot on the right. Note the blue marker showing that I am drag and dropping the tab. PLEASE don't close this bug or move it again, it's a real thing and it's tiring to have to keep re-logging it so that the right people see it.
*** Bug 1216704 has been marked as a duplicate of this bug. ***
(In reply to pallas wept from comment #0) > PLEASE don't close this bug or move it again, it's a real thing and it's > tiring to have to keep re-logging it so that the right people see it. You just keep re-filing the same thing. I resolved them as duplicates because they were duplicates. (bug 1216704 and bug 1215137). Assume that we know what we are doing. Bugzilla bugs are for tracking technical defects, not your support cases. I am adjusting the bug summary to your previous summary and I'll move it to the right please.
Yes, I do keep re-filing it, and I explained why. Like I explained, I was re-filing it because if it was filed it in certain places, it would be seen, and if not, then it wouldn't, and it was being either initially filed, or moved, to the places where it wouldn't be seen. I did explain this when I re-filed it - in the correct place where it would be seen. It's been months trying to get attention paid to this technical defect - and this is not a support issue, this is a technical defect. It's specifically broken on opensuse KDE Wayland. Works just fine on Ubuntu KDE Wayland or opensuse KDE X11 or opensuse Gnome Wayland. Isn't specific to my machine or anything I do, occurs without any change being made to the package, as it ships - as I showed in the reproduction steps given above. I'm not looking for tech support, I'm looking to un-break this package. Assume I know what I'm doing, too, huh? I'll be sure to let you know when I'm not sure. You've changed the title to be relevant for the bug as it was when I started reporting it months ago, you can see from the screenshots that the behaviour has changed - the full list will appear and is scrollable, now. But you still can't drag tabs in it - UNTIL, as I discovered yesterday, it has been as long as the screen, in the current session (see attached screenshots) You ask me to assume you know what you're doing but then you change the title to be inaccurate because you won't talk to me about this bug so you don't know what's happening with it. I'm just trying to get a broken package fixed, what is wrong with that? Why am I being treated like a leper for this?
This also happens with Firefox nightly built by Mozilla - I just tried out https://download-installer.cdn.mozilla.net/pub/firefox/nightly/latest-mozilla-central-l10n/firefox-121.0a1.en-GB.linux-x86_64.tar.bz2 and it was exactly the same, can't drag-n-drop tabs in the all tabs list to re-order them, until you create enough tabs that the list fills the entire page, then it works...but this was not the openSUSE packaged Firefox, this is just the pre-built nightly, with a clean profile.... so perhaps this is caused by some interaction between FF and the KDE Wayland session? I also found more interesting behaviour to replicate this. It doesn't need to have the all tabs list the full length of the screen. It only has to go just past the bottom of the window. For example, if I un-maximize the window, and resize it to half the screen, and move it to the top half of the screen, then I needed 19 tabs - enough to make 3 tabs overlap the bottom of the window, and then it would work. If I resize to 1/4 of my screen, I needed only 8 tabs to make it work. At the smallest height it would allow me to resize, I could make the list work with just 4 tabs (plus the extra menu items above the tab list) On top of this, if I maximise the window when it is tiny short like this and the list is working, when I maximise it, the list stops working again, I can't drag-n-drop... and when I un-maximise, it immediately works again. When it is crazy short and working, if I resize the window to be taller than the all tabs list, if the all tabs list is open when I resize, it will continue to work, until I close the list and re-open it, and it stops working again and I can't drag-n-drop any more. If I then resize the window to be shorter than the all tabs list, short enough that it would have worked before, it won't work, until I create a new tab, and that kicks it off and it works. The browser tools console returns an error when the failure occurs: browser.ui.interaction.alltabs_menu - Unknown scalar.
> Bugzilla bugs are for tracking technical defects How's this one tracking? It's a pain to have to resize the window so I can rearrange my tabs.
*** Bug 1219329 has been marked as a duplicate of this bug. ***
(In reply to hui from comment #6) > *** Bug 1219329 has been marked as a duplicate of this bug. *** @hui, if you resolve the plasma bug, and keep this one open, that suggests that this is confirmation that this is a bug in the firefox package, and not the plasma package - but then, how does this happen with the stock firefox nightly download, which is not packaged by suse? If this is a problem with the firefox package, what's going on with it? It's been 5 months and I haven't heard a word, except from you telling me it could not be reproduced, and must be specific to my machine, but when I gave you reproduction process using the tumbleweed ISO in a VM (so, obviously not machine-specific), you did not reply. Tell me something!? The only reaction I'm getting is to repeatedly silently close my cases as duplicates and no comments other than complaints that I'm a noob (which is true, but I can't help that, and I'm trying!), and no action. I'm sure you can understand why this is becoming frustrating after such a long time without any correspondence.
(In reply to pallas wept from comment #7) > It's been 5 months and I haven't heard a word, except from you telling me it > could not be reproduced Which I do appreciate, by the way, since as far as I'm aware (which doesn't make it a fact, but the fact is that it is all I am aware of), your few minutes testing this are the only time or effort invested even attempting to look into this in the entire 5 months. So at least I know that you *tried* - so thanks for that. But I gave you those reproduction processes to bypass my machine as a factor, and you went silent. You were my only hope, and now I have none. I feel like there is an off-the-record agreement that nobody will look into my issues and they will all be resolved as duplicates of this bug to be ignored forever, because I am new to bugzilla and filed my first two cases according to outdated documentation of how to file them, and because I did it wrong, and presented a difficult issue, I have become an annoyance and must be punished for eternity. This really sucks, and it isn't a cool way to treat people. I respect that you are all busy, but 5 months without a word goes beyond "I'm busy" to "I'm deliberately ignoring you". I've re-opened the other case because it is NOT a duplicate of this one, it's a separate bug filed against a separate project, intentionally, and since you are not talking to me, and nobody is, no reason has been given by anyone to suggest that there is any reason to close that one. If anything, from a technical perspective (since the issue DOES exist in plasma wayland, and also NOT in suse's firefox package), closing this bug as a duplicate of that one, seems to make more sense at the moment. Since you obviously have no desire or intention to interact with me, perhaps doing that and leaving it to another team might suit you better, too.