Tested this issue on Ubuntu 14.04 using chrome reported version stable # 58.0.3029.81 & Chrome latest stable # 58.0.3029.96 by following steps mentioned below.

1.Opened several tabs in a single Chrome window 
2.Clicked and hold on one tab and start dragging it(Didn't release the mouse button) and Moved down so that the tab detached into a new window
3.Dragged it back moving the cursor into between existing tabs in a different position than the original tab was and now released the mouse button
4.Observed tab dropped to the position where I dropped it and not at its original position.
5.Tried 4-5 times but unable to repro the Issue

	
teo8976@ Could you please find the attachment and confirm if anything is missed in triaging the issue. If possible please provide screencast for better understanding the Issue and if you are using any specific Windows manager.

Deleted: 719436.ogv 920 KB

	719436.ogv 920 KB View Download

You are not supposed to release the mouse button at step 2.
Steps 2-5 should be done in a single drag-n-drop motion.

Also try repeating steps 3-4 many times rapidly (all without ever releasing the mouse button), and/or moving the cursor around crasily. That *might* help make the issue more likely to trigger.

Other than that, it may be you just don't observe it. As I said, it doesn't always happen. I may have exaggerated saying "almost half of the times".

I am using Unity. Ubuntu 16.04, though.

Thank you for providing more feedback. Adding requester "mmanchala@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

Tested this issue on Ubuntu 16.04 using latest chrome version #60.0.3088.3 as per the steps mentioned in original comment #0 and comment #1.

@teo8976: Could you please find the attached screen cast and confirm that's the issue you're facing? if possible please attach a expected screen cast for further investigation.

Thanks!

Deleted: May 12 2017 11-37 AM.webm 3.5 MB

	May 12 2017 11-37 AM.webm 3.5 MB View Download

> @teo8976: Could you please find the attached screen cast and confirm 
> that's the issue you're facing?

From the screencast I can't tell when you released the mouse button. If it is at minute 0:22, then it seems like expected behavior (the tab is dropped where and when you release the mouse button). If otoh you had not released the mouse button yet, then it would be a slightly different issue, the window being dropped unexpectely without releasing, but at the place where the cursor is rather than in its origina position.

I do observe an unexpected thing in your screencast: when the tab is "detached" into a new window, it does not always follow the mouse cursor, it remains in a fixed position. That seems unrelated to the issue at hand however (and most probably is a general issue with the window manager: the window tends to "stick" to screen edges in a rather unpredictable and inconsistent way).


Have you tried with a tab where you have previously loaded a page (and load some pages into the other tabs too), as opposed to an empty tab?

Thank you for providing more feedback. Adding requester "sandeepkumars@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

pwnall@ Could you please take a look in to this issue.

Thanks!

This is a Chrome UI issue, doesn't have anything to do with web platform (i.e. drag/drop of content into/out of web content), so not Blink>DataTransfer

Updating component appropriately.

@Could someone from browser>tabstrip team please look into this .

Thanks!

It sounds like the original report is talking about something different than the screencast in comment 4, which may or may not be problematic as well.

This looks likely to be Linux-specific, maybe for particular WMs or something.  I think thomasanderson has worked the most with this kind of thing recently.

Un-duping.  The screencast in c#4 is a separate issue

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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