Chrome "activates" on wrong desktop
Reported by
jeff.1...@gmail.com,
May 25 2017
|
||||||
Issue descriptionChrome Version : Google Chrome 58.0.3029.110 (Official Build) (64-bit) Revision 691bdb490962d4e6ae7f25c6ab1fdd0faaf19cd0-refs/branch-heads/3029@{#830} OS Windows URLs (if applicable) : Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Firefox: IE: What steps will reproduce the problem? (1) Install a version of windows (eg. Server 2010) That allows multiple desktops. (2) Open one desktop using "Remote Desktop" and start chrome (3) Open a second desktop and try to run Chrome What is the expected result? Chrome opens a window on the second desktop. What happens instead? Chrome sends an "activation event" to the copy on the first desktop, which is, of course, ignored, and then it just sits there doing nothing and the second user has to either kill chrome using task manager before running or has to run a different browser instead. Please provide any additional information below. Attach a screenshot if possible.
,
May 25 2017
I believe the "remote desktop" that this bug refers to is Microsoft's RDP, not Chrome Remote Desktop. FWIW, we have a similar problem on Linux, where Chrome can't handle being run on two different desktops using the same profile. I suspect that the problem will go away on Windows as well if the --user-data-dir parameter is used to tell one of the two instances to use a different profile directory. If you sign in to Chrome, then bookmarks etc. will be synced, which might be an acceptable workaround for your use-case.
,
May 26 2017
,
May 29 2017
,
Jun 14 2017
Running with "--user-data-dir=C:\mydir" does indeed seem to work as a temporary workaround. Syncing bookmarks is neither needed nor desirable in my use case because this is a shared computer.
,
Jun 14 2017
Thank you for providing more feedback. Adding requester "kavvaru@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
,
Jun 14 2018
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 |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ligim...@chromium.org
, May 25 2017