"Ghost" browser window on the desktop after restarting Chrome [Mac] |
||||||
Issue descriptionVersion: 51.0.2704.106 OS: macOS 10.11 What steps will reproduce the problem? (1) In Chrome Start up preferences, choose the option to Continue where you left off (2) Create four browser windows with different URLs (the exact number 4 probably is not important); call these windows A, B, C, and D (3) Miniaturize A, B, and C to the dock, in that order (4) Restart Chrome What is the expected output? Windows A, B, and C should be restored to the dock, and window D should appear on the desktop What do you see instead? Windows A, B, and C are in the dock, and window D is on the desktop, but a "ghost" version of window A is also present on the desktop. Clicking the ghost window does not make it the main window, and using Cmd ` to cycle through windows causes the ghost window to disappear, and window A to deminiaturize from the dock.
,
Jul 15 2016
Here's me failing to repro with the same versions of Chrome and macOS. Let me know what I did wrong.
,
Jul 15 2016
I was getting ready to respond with more info yesterday but could not reproduce the bug :-/. I was reproducing it "at will" before that. I got up this morning and was able to reproduce it. Yesterday at some point one of the corp extensions was causing a modal dialog to appear on launch which I was concerned would get in the way of smooth reproduction of the problem so I disabled all extensions (--disable-extensions). On a hunch I omitted that flag this morning and the problem returned. So now I'm guessing the BeyondCorp or some other extension is doing something at startup time that causes the browser window to pop onscreen even though it's in the dock. Either causing drawing to the window, or asking for some window property, or forcing the window to be visible is my guess. I'm not sure what's possible with the extension API. If you can reproduce this, perhaps don't spend tons of time on it if it turns out to be tricky to track down. I'm assuming no one has reported this bug before. Here's a link to a movie showing the problem in action. It's too large to attach directly to the bug. https://drive.google.com/a/google.com/file/d/0BwcLL5PHtZQHa1AxeVEwOC1vcVE/view?usp=sharing
,
Jul 15 2016
Super interesting! I won't actively work on it right now, but I'll keep an eye out for anything suspicious as I go over other session restoration stuff.
,
Feb 23 2017
Archiving; feel free to reopen if it gets user reports or reliable repro. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 Deleted