Cannot drag tabs after dragging a tab out of the window
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: nanoblade9, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
Steps to reproduce:
- Open 3 tabs
- Drag one of the tabs out of the window to create a new window
- Try to reorder tabs in the first window by dragging them
Actual results:
In 99% of times, tabs cannot be dragged anymore until Firefox is restarted.
Expected results:
Tabs can still be dragged.
Comment 1•9 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
As it turns out, it's not just tabs. I can't drag anything at all. Selected text, images, bookmarks, sites on the new tab...
Comment 3•8 months ago
|
||
I confirm that this bug is real and occurring at present
I used to be able to drag tabs to arrange it & was able to drag a tab out to make a new window or to drag a tab onto an existing window to consolidate it.
Now (28 May 2024) none of this works. a reboot solves it for a few minutes or a first drag. but its broken after that.
Using Ubuntu 22.04. been on it for 2 years and it worked fine. not sure if something on an OS update or FF update that broke it.
Comment 4•8 months ago
|
||
It sounds like the drag&drop session is not ending properly, that is implemented per platform so moving to GTK Widgets
I've also been experiencing this bug for a few days now: when it occurs, tooltips no longer appear (neither on tabs, nor on user interface buttons, nor on DOM elements with a title
attribute).
Seems to be working for me now on 126.0.1, Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0
This seems to happen when you drag a tab (or even a DOM element (link, image, ...)) and release it very quickly (before the drag icon or preview appears, less than half a second after the drag was initiated).
So there's a good chance that this will regularly happen accidentally.
I don't have this issue in 126.0.1. Looks like it's a duplicate of bug 1897115.
Updated•8 months ago
|
Description
•