Errata:

I. Steps say 1,2,2,3,4,5,6 but they should read 1 to 7.

II. Any references to Chromium (steps 2 and 4) should read "Chrome". I am used to Chromium, but this should make no relevant difference at all.

Tested the issue on windows 10 using chrome latest stable M61 #61.0.3163.79 and followed the steps mentioned in comment #0 and unable to reproduce the issue.

Attached screencast for reference.

@ alvarezp-- Could you please try in latest stable and also please check attached screencast and confirm us if we had missed any steps in reproducing the issue and also help us with the screencast for better understanding.

Thanks!

Deleted: 757853.mp4 3.5 MB

	757853.mp4 3.5 MB View Download

Thank you for trying to reproduce the issue.

Step 6 was not followed correctly. You launched Chrome and, once open, you opened example.net. The correct way is to launch the command "chrome http://example.net/". There are two ways of doing this:

* Hit Win and just type "chrome http://example.net/". This will use the Search bar to launch Chrome with the parameter.

* Open the Command Prompt, switch to the Chrome directory (on my PC this is done by doing 'cd "C:\Program Files (x86)\Google\Chrome\Application"' and then running "chrome http://example.net/".

For an example on Chromium under Linux please watch https://youtu.be/tWE8EByo2k0 as reported on  bug #449616 . The behavior is the same as on Windows except that on Linux I had "focus stealing prevention" enabled.

Thank you,
Octavio.

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

Able to reproduce this issue on reported version 58.0.3029.81, latest stable 62.0.3202.89 latest canary 64.0.3261.0 using Windows 10 and the issue is seen from M-50 (50.0.2641.0). Hence considering this issue as Non-Regression and marking it as Untriaged.

Note: Its a Windows specific issue

Thank you for reproducing the issue. Hopefully this helps moving it forward.

However, please clarify why have you stated that this is a Windows-specific issue, as I have mentioned that this is reproducible under Linux, I have provided a video proof of the issue occurring under Linux, and I have even provided a reference to  bug #449616  which is way older than this bug and it has been closed due to inactivity but remains unfixed.

This is a multiplatform issue.

Video proof of this issue occurring under Linux is included on  bug #449616  but I also paste it here for reference:

https://youtu.be/tWE8EByo2k0

Thanks.

Correction to the c#5
Issue is reproducible on ubuntu 14.04 and Mac 10.12.6 also

Still unfixed...

It's very simple to fix on windows... (but maybe impossible on linux?)

https://docs.microsoft.com/windows/desktop/api/shobjidl/nn-shobjidl-ivirtualdesktopmanager

**Mass UI Triage**

This issue is still reproduced on Windows 10 OS from M60 to latest canary-72.0.3618.0.Could some one from dev please take a look.

Thanks..!!