New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 728695 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Task

Blocked on:
issue 769755
issue 774126
issue 793916

Blocking:
issue 672961
issue 731255



Sign in to add a comment

[Meta] Make Exo work when ash and chrome browser are still in the same process

Project Member Reported by varkha@chromium.org, Jun 1 2017

Issue description

Ideally using some porting layer that would make transition to full ash-chrome separation easier.
 
Cc: rjkroege@chromium.org sadrul@chromium.org reve...@chromium.org
Ideally, I think we'd like to see exo use a separate WindowTreeHost so that we don't introduce a new code path in the window server and viz for local windows. However, Sadrul was concerned that there's a lot of input work involved here. I've added Sadrul for comments.
Blockedon: 678270
Blockedon: 729028
Blocking: 731255
Blockedon: -678270
Blockedon: -710826
Blockedon: 766184
Blockedon: 769755
Blockedon: 774126

Comment 10 by sky@chromium.org, Nov 3 2017

Status: Started (was: Assigned)
Blockedon: -766184
Blockedon: 793916
Blockedon: -729028
Status: Fixed (was: Started)
Components: -Internals>MUS Internals>Services>WindowService

Sign in to add a comment