New issue
Advanced search Search tips

Issue 670731 link

Starred by 8 users

Issue metadata

Status: Assigned
Merged: issue 670235
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Full-screen windows overlap on restart/restore w/ multiple profiles/windows.

Project Member Reported by d...@chromium.org, Dec 2 2016

Issue description

Chrome Version       : 57.0.2939.0 (Official Build) canary (64-bit)
URLs (if applicable) : N/A
OS version           : 10.12.1 (16B2555)

What steps will reproduce the problem?
(1) Install two Chrome profiles.
(2) For Profile A, open a full-screen window. For Profile B, open two full-screen windows. (I full-screen one and hit Command+N for the second). NOTE: You may need to open two for Profile A, too. I think I can repro without though.
(3) After everything is in place, you should have three full-screen windows, so three desktops spaces.
(4) Restart Chrome via: chrome://restart
(5) Wait for Chrome to settle.

What is the expected result?
I would have the same layout: three full-screen windows, one from Profile A and two from Profile B, each in their own full-screen space.

What happens instead?
One window from each profile gets its own full-screen space, and the second window from Profile B is not full-screen and is overlaid on top of Profile A's full-screen space.

(See attached screenshot).

This seems similar to  crbug.com/665230 , but I think it is a bit different b/c this is on restart/restore instead of during live manipulation. Marking P2 b/c it affects user experience, most notably the seamlessness of upgrades and cost of restart, but isn't too bad IMO.

I believe this bug has been around for a while.
 
Screen Shot 2016-12-02 at 08.48.29.png
290 KB View Download

Comment 1 by ajha@chromium.org, Dec 5 2016

Labels: M-57
Cc: spqc...@chromium.org
Mergedinto: 670235
Status: Duplicate (was: Unconfirmed)
Assuming this issue similar to #670235 , duping this to  issue 670235 .


Status: Unconfirmed (was: Duplicate)
 Issue 670745  has been merged into this issue.
Status: Untriaged (was: Unconfirmed)
Tested on mac os 10.11.6 using chrome latest canary M57 #57.0.2944.0 and issue is reproduced.

Marking it as untraiged.

Thanks !
Cc: -spqc...@chromium.org
Owner: spqc...@chromium.org
Status: Assigned (was: Untriaged)

Comment 8 by kpreid@google.com, Jan 22 2018

I have what I think is this problem too and would like to see it fixed as sorting out my windows to be correctly fullscreen and on the correct monitor/desktop is the main annoyance of restarting Chrome for me (outside of in-web-page state that isn't exactly Chrome's problem).

From my impression of what happens when I restart, I do not think multiple profiles are necessary to trigger it, just many fullscreen windows. And for me, it used to be that windows would end up on top of fullscreen windows but now more often windows simply fail to go fullscreen (end up on the regular desktop). (This might be affected by OS version?)

I also _suspect_ it has something to do with the macOS going-to-fullscreen animation and that a dubious workaround would be to wait for each one to complete before creating/fullscreening another window.

Comment 9 by grt@chromium.org, Jan 22 2018

Components: UI>Browser>Sessions

Comment 10 by grt@chromium.org, Jan 22 2018

Cc: shrike@chromium.org
shrike@: what's the right way to get this into the Chrome on Mac triage queue? this issue has been identified as a pain-point for browser restarts. thanks.
Cc: -shrike@chromium.org ellyjo...@chromium.org
Hello grt@,

This bug is currently assigned to a Mac engineer so it doesn't need to be retriaged. +ellyjones@ who can adjust its priority.
Labels: -Pri-2 Pri-1
We can up this to Pri-1 since it's a user pain point.

spqchan: can you take a peek? :)
Owner: ----
Status: Untriaged (was: Assigned)
Labels: -M-57 Target-71 M-71
Owner: sdy@chromium.org
Status: Assigned (was: Untriaged)
sdy@, over to you :)

Pri-1 for M71 - let's see if we can get it into that release.
Cc: thomasanderson@chromium.org sdy@chromium.org weili@chromium.org
 Issue 888337  has been merged into this issue.

Comment 16 Deleted

Sign in to add a comment