New issue
Advanced search Search tips

Issue 640392 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 689665
issue 640394

Blocking:
issue 640365



Sign in to add a comment

Immersive mode shouldn't create title window as sibling of window showing immersive for

Project Member Reported by sky@chromium.org, Aug 23 2016

Issue description

When entering immersive mode mash creates a new Window to host the reveal. Currently this window is created as a sibling of the window immersive mode is shown for. This is problematic in so far as the rest of ash is likely not going to expect this window to exist in the same container (for example, I suspect it'll get a shelf entry).

Ideally the reveal window should be a child of the window in immersive. But mus disallows this. Specifically once a client has been embedded in a window then owner of the window can no longer add children to that window. We need to relax this constrain (for the windowmanager) in order to get the reveal to work correctly.
 
Components: MUS
Labels: Proj-Mustash
Components: Internals>MUS

Comment 4 by sky@chromium.org, Feb 7 2017

Blockedon: 689665

Comment 5 by sky@chromium.org, Feb 8 2017

Blockedon: 640394

Comment 6 by sky@chromium.org, Feb 8 2017

Blocking: -548435 640365

Comment 7 by sky@chromium.org, Feb 8 2017

Owner: sky@chromium.org
Status: Fixed (was: Untriaged)
I made it so the window is marked as transient, so hopefully there aren't any side effects.

Comment 8 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 9 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 11 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)
Components: -Internals>MUS Internals>Services>WindowService
Components: -MUS

Sign in to add a comment