services/ui/surfaces => components/display_compositor? |
||||||||||||
Issue descriptionWe'd like to move display compositor code to a central location so that it can be used by both Chrome and Mus+Ash. Currently it lives in services/ui/surfaces which means it depends on Mus which isn't ready yet to be used in production code. Perhaps we can move code over to components/display_compositor instead.
,
Dec 1 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/be20bdb9c70614fab6cbc775e2da886e9af4c30a commit be20bdb9c70614fab6cbc775e2da886e9af4c30a Author: fsamuel <fsamuel@chromium.org> Date: Thu Dec 01 23:12:21 2016 services/ui/surfaces should not depend on other parts of Mus The display compositor should be a separable component of Mus. BUG= 670458 TBR=rjkroege@chromium.org Review-Url: https://codereview.chromium.org/2545923003 Cr-Commit-Position: refs/heads/master@{#435751} [modify] https://crrev.com/be20bdb9c70614fab6cbc775e2da886e9af4c30a/services/ui/gpu/gpu_main.cc [modify] https://crrev.com/be20bdb9c70614fab6cbc775e2da886e9af4c30a/services/ui/surfaces/BUILD.gn [modify] https://crrev.com/be20bdb9c70614fab6cbc775e2da886e9af4c30a/services/ui/surfaces/display_compositor.cc [modify] https://crrev.com/be20bdb9c70614fab6cbc775e2da886e9af4c30a/services/ui/surfaces/display_compositor.h
,
Jan 22 2017
,
Jan 23 2017
I'll take ownership of this one.
,
Jan 26 2017
,
Feb 6 2017
Not actively working on this so I'm marking as Available.
,
Apr 19 2017
,
May 3 2017
,
May 23 2017
,
Jun 13 2017
This has been relocated to components/viz. Marking as FIXED.
,
Jun 13 2017
,
Feb 26 2018
,
Feb 26 2018
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by fsam...@chromium.org
, Dec 1 2016Components: MUS
Labels: displaycompositor