Closed
Bug 1482652
Opened 6 years ago
Closed 6 years ago
When creating a new window by detaching existing tab and moving it to a different monitor, the new window is opened on the original monitor
Categories
(Firefox :: Tabbed Browser, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1483786
Tracking | Status | |
---|---|---|
firefox63 | --- | affected |
People
(Reporter: jb.massey, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180811103606 Steps to reproduce: On Windows 10 (April 2018): Given a Firefox window on Monitor X (any monitor), click and drag an existing tab to detach it from the window and create a new Firefox window, then drag it to the top, approximately center, of Monitor Y (any other monitor) and release. Actual results: A new Firefox window containing only the detached tab is created and maximized on Monitor X. Expected results: A new Firefox window containing only the detached tab is created and maximized on Monitor Y.
Summary: When creating a new window but pulling a tab off AND moving it to a different monitor, the new window is opened on the original monitor → When creating a new window by detaching existing tab and moving it to a different monitor, the new window is opened on the original monitor
- I was able to reproduce on a new profile - I also tested this on my Mac (High Sierra 10.13.5): - When I started up Firefox on the Mac, the build was 63.0a1 2018-08-04 and the behavior was as Expected above, but after updating to 2018-08-11, I was able to reproduce the bug.
Hi jb.massey, Thanks for reporting this bug. I am able to reproduce this bug with version 63.0a1. Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180815100249
Status: UNCONFIRMED → NEW
status-firefox63:
--- → affected
Component: Untriaged → Tabbed Browser
Ever confirmed: true
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•