Thanks for filing the issue.
@Reporter,
Could you please elaborate on step:4 from the above for better understanding the issue and if possible please provide us the screencast to triage the issue further.

Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Fun side note, Opera does not have this bug.

Checked the issue on reported version 59.0.3063.4, latest stable 61.0.3163.100 and on latest canary 63.0.3236.0 with the mentioned steps in comment#0 on Ubuntu 14.04. Unable to reproduce the issue. Attaching screencast for reference.


@Reporter: Could you please let us know if we missed any steps and Could you please check this issue by upgrading chrome to latest stable M61-61.0.3163.100 and please let us know if the issue still persist or not.

Thanks!

Deleted: 709762.ogv 3.5 MB

	709762.ogv 3.5 MB View Download

Just checked, the bug is still there.

2 things you did wrong when trying to reproduce:
 - You dragged the tab to an existing window, you need to let the tab create its own window instance
 - You need multiple monitors, in the above video I've captured my monitor 1 and 2 screens and put them next to each other, this will not work with just one

If you can, please watch the video I provided, it really does show the few needed steps to reproduce the bug.

Thank you for providing more feedback. Adding requester "kebalaji@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Here a video with audio "explaining" my actions (sorry about the background noise), hopefully this is a bit better at explaining the problem: https://youtu.be/sxdMdxYTYdM

Unable to reproduce this issue on Debian Rodete with chrome stable #66.0.3359.117 as per steps mentioned in the comment #0

Attaching the screen-cast for reference.

cra0zy@ Could you please upgrade chrome to latest version and re-try the scenario on clean profile with no apps & extensions and let us know your observations.

Thank You...

Deleted: 709762.mp4 20.5 MB

709762.mp4 20.5 MB Download

I can still reproduce it, looking at your video, I see your error:

You need to drag the tab to the second screen, not drag the tab than move the window.

If by some chance you can't drag the tab to the second screen, try reproducing it in GNOME.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested this issue on chrome stable 66.0.3359.139 using windows-10 unable to reproduce this issue as we don't have linux dual monitor setup. hence forwarding this issue to Inhouse Team, any one of the team have a look on this issue.
Attaching Screencast for reference.


Thanks..!

Deleted: 709762.mp4 4.1 MB

	709762.mp4 4.1 MB View Download

Its a Linux only issue as stated in the title.

Tested the issue using #66.0.3359.139 on Linux Debian Rodete using external monitor, as per the steps mentioned in original comment. On exiting fullscreen, chrome is staying on the same screen.

Removing TE-NeedsTriageFromHYD as this issue isn't repro from our end.

Adding UI>Shell>MultipleMonitor component for further triaging of the issue.

Thanks!!

As the issue is not reproducible from our end as per comment#5, #10, #13 and #15, hence adding label "TE-NeedsTriageHelp" and requesting some one from Dev team to have a look into this issue and help in further triaging it.

Thanks!