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

Issue 596562 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 612637
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 548429



Sign in to add a comment

mus/ozone screen manager

Project Member Reported by rjkroege@chromium.org, Mar 21 2016

Issue description

Ozone window manager needs a display manager.
 
Additional issue as part of this bug: fix the plumbing of resize into command_buffer_driver.cc so that gbm buffers get built with the right size.
NB: This bug corresponds to the mustash1 version.

Comment 3 by sky@chromium.org, Apr 7 2016

mus can communicate multiple displays already. Can you expand on what is needed here?
pixel mus can drive only a single output screen. It needs feature parity with existing CrOS.
Blocking: 548429
Cc: fsam...@chromium.org sadrul@chromium.org osh...@chromium.org spang@chromium.org
Summary: mus/ozone screen manager (was: mus/ozone display manager)
We need a mojo service for configuring the screen.
Labels: displaycompositor
This seems displaycompositor related. Adding label.
Mergedinto: 612637
Status: Duplicate (was: Started)
Blocking:
Components: Internals>Services>WindowService
Components: -MUS>Phase>1

Sign in to add a comment