Closed Bug 1714416 Opened 5 years ago Closed 4 years ago

You can no longer drag a tab out to empty desktop space to create a new window. (If you do it fast enough)

Categories

(Firefox :: Untriaged, defect)

Firefox 88
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: anton.dahlgren, Unassigned, NeedInfo)

Details

(Whiteboard: QA-not-reproducible)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

I tried to move a tab from my main monitor to second monitor to create a new fullscren window. Click and quickly drag tab to second monitor.

Actual results:

Multiple outcomes. 1. Nothing happened
2. It became a window but stayed on the same monitor
3. It became a window but stayed on the same page but slightly smaller than original window
4. It went on to the second monitor but didn't go fullscreen.

Expected results:

New firefox window with the same size as the old one being created on the second monitor. Even if you are moving the tab very fast.

It is the same on update 89

Hey Anton,
I tried reproducing this issue on the latest versions of Firefox Nightly 91.0a1 (2021-06-08), beta 90.0b5 and release 89.0 but couldn't repro it.

Can you test the issue while in Safe Mode? You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .
Also a fresh new profile could help. You can find more about creating a new profile here : https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile .
If possible, you can test this issue on the nightly build as well. Download the build from : https://www.mozilla.org/en-US/firefox/nightly/all/ .

Flags: needinfo?(anton.dahlgren)
Whiteboard: QA-not-reproducible

Marking this as Resolved > Incomplete due to reporter's lack of response.
If the issue reoccurs or still persists feel free to re-open or file a new bug.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.