No, I don’t think so. You can drag out windows but they don’t for example snap to the corners immediately, so you have to release them first and then pick them up again.
I looked into it further at one point, there’s some other change that needs to happen before that feature can me implemented. The issue was documented over a decade ago… but I’d have to learn a ton about how FF works to even start to understand how to make the changes needed.
I can say that for now, the logic is pretty basic, hide the tab, attach a little screenshot of the tab to the cursor, create a window with the content of that tab if the mouse is released outside of the browser window.
I don’t understand how you don’t notice the difference between how chrome handles dragging tabs and how FF does. And all the people who upvoted you too.
We must have very different ways of using our computers. I’m regularly dragging a tab out to put it side by side with another window, and it seems like FF tabs are the only thing I drag around that don’t behave as expected. It’s glaringly obvious every time it happens, and it’s minuscule friction points like this that drive me nuts when I run into them repeatedly, day after day, for years.
Edit: the behaviour with FF is, you drag the tab out of the original FF window, release your mouse. A new window is created, then you can drag that window around place it as usual.
No this is actually working perfectly, on Wayland.
Drag, i get a miniature transparent window, move to other window, place next to a tab and that needle appears, done.
So dragging a tab to another window works. But true, dragging a tab and it immediately becomes a window doesnt. But that is quite aggressive UI wise, so I think its fair to not add it.
Isn’t this already built in?
No, I don’t think so. You can drag out windows but they don’t for example snap to the corners immediately, so you have to release them first and then pick them up again.
I looked into it further at one point, there’s some other change that needs to happen before that feature can me implemented. The issue was documented over a decade ago… but I’d have to learn a ton about how FF works to even start to understand how to make the changes needed.
I can say that for now, the logic is pretty basic, hide the tab, attach a little screenshot of the tab to the cursor, create a window with the content of that tab if the mouse is released outside of the browser window.
Maybe I’ll dig into the code again at some point
I don’t understand how you don’t notice the difference between how chrome handles dragging tabs and how FF does. And all the people who upvoted you too.
We must have very different ways of using our computers. I’m regularly dragging a tab out to put it side by side with another window, and it seems like FF tabs are the only thing I drag around that don’t behave as expected. It’s glaringly obvious every time it happens, and it’s minuscule friction points like this that drive me nuts when I run into them repeatedly, day after day, for years.
Edit: the behaviour with FF is, you drag the tab out of the original FF window, release your mouse. A new window is created, then you can drag that window around place it as usual.
i can drag tabs from window to window, don’t know how you all use your computers…
No this is actually working perfectly, on Wayland.
Drag, i get a miniature transparent window, move to other window, place next to a tab and that needle appears, done.
So dragging a tab to another window works. But true, dragging a tab and it immediately becomes a window doesnt. But that is quite aggressive UI wise, so I think its fair to not add it.
who the fuck uses chrome??