Closed Bug 949320 Opened 11 years ago Closed 8 years ago

Dragging tab to an empty second monitor opens window on the wrong monitor

Categories

(Core :: Widget: Cocoa, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: MattN, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: polish, regression, reproducible, Whiteboard: [parity-safari][polish-hard][polish-interactive][polish-p2][tpi:+])

+++ This bug was initially created as a clone of Bug #465186 +++

If a tab is detached and dropped at a given point on another monitor, the new window that is opened will be located near the window that contained the tab instead of on the other monitor where the tab is dropped.

The fix from bug 465186 still works in the single monitor case but not when I drag to another.

OS X 10.7 & 10.9

Last good revision: dac5700acf8b (2012-10-17)
First bad revision: cb573b9307e5 (2012-10-18)
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=dac5700acf8b&tochange=cb573b9307e5

I suspect the cause is bug 794038.
Since you commented in bug 465186 comment 75 and 76, can you see if the same regression range applies to Windows 7 and Linux?

Confirm that this works on a build from
  http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/10/2012-10-17-03-05-48-mozilla-central/
and fails with a build from
  http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/10/2012-10-18-03-06-18-mozilla-central/
Flags: needinfo?(sguha)
Flags: needinfo?(sabrage)
Confirmed working with both 2012-10-17 and 2012-10-18 but not the latest Nightly.
Flags: needinfo?(sabrage)
(In reply to sabrage from comment #2)
> Confirmed working with both 2012-10-17 and 2012-10-18 but not the latest
> Nightly.

OK, please file a new bug (CC me) and, if possible, use mozregression[1] to find the regression range.

[1] http://mozilla.github.io/mozregression/
I have this problem with windows 7 x64 sp1 in 31.0. but it only happens the first time, 2nd and 3rd time it works fine. 

I have 3 monitors. I dragged it onto the 3rd empty monitor. tb has no problem interestingly enough and neither do any other programs I have. I should try tb drag after reboot and see what happens.
oops. my issue is dragging the whole application window. but maybe this info will be interesting just the same.
Flags: needinfo?(sguha)
I can reproduce in Firefox 48.0.1 and OS X 10.11.6
There have been some recent fixes that may be relevant to this. Can you reproduce with current Developer Edition (Firefox 50) or Nightly (51) builds?
Priority: -- → P2
Whiteboard: [parity-safari][polish-hard][polish-interactive][polish-p2] → [parity-safari][polish-hard][polish-interactive][polish-p2][tpi:+]
I've just tried on Nighly `51.0a1 (2016-08-24)`, the functionality works (dragging a tab back and forth a secondary monitor), however I could notice a visual glitch.

When you grab a tab, a small transparent thumbnail of the page which follows your mouse. That thumbnail is confined to the monitor the tab originates from, and doesn't follow the mouse if it goes to a secondary screen. The thumbnail glitches here and there in the original monitor, until the cursor doesn't return to it, where then it follows the mouse again.
(In reply to Vittorio Giovara from comment #8)
> I've just tried on Nighly `51.0a1 (2016-08-24)`, the functionality works
> (dragging a tab back and forth a secondary monitor), however I could notice
> a visual glitch.
> 
> When you grab a tab, a small transparent thumbnail of the page which follows
> your mouse. That thumbnail is confined to the monitor the tab originates
> from, and doesn't follow the mouse if it goes to a secondary screen. The
> thumbnail glitches here and there in the original monitor, until the cursor
> doesn't return to it, where then it follows the mouse again.

Could you file a new bug and tell us a bit more about your setup? I'm especially interested in the number of monitors (including internal ones), their resolution and how they are arranged (for example, retina macbook in middle and one external monitor on each side etc). I'm unable to reproduce this particular glitch at the moment. Thanks!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.