Implement a DisplayProvider for content, and pull out viz::Display init code out of GpuProcessTransportFactory |
||||||
Issue descriptionMost of the code in GpuProcessTransportFactory belongs in the Viz service including creation of the viz::Display, the BeginFrameSource, and the OutputSurface. We should create a new DisplayProvider that moves that functionality out of GpuProcessTransportFactory. That DisplayProvider is then passed into FrameSinkManagerImpl's construction. The end state of this work is DirectLayerTreeFrameSink goes away, and instead content uses RootCompositorFrameSinkImpl for UI. Initially, we may not use a Mojo MessagePipe but we will still use raw pointers to mojo interfaces in UI.
,
Oct 2 2017
,
Oct 3 2017
,
Oct 25 2017
Not working on this currently.
,
Oct 25 2017
Is this WontFix cuz you're doing this another way?
,
Oct 30 2017
This is potentially a WontFix. It's an intermediate step between how things work today and how --enable-viz would work. If we move straight an out of process display compositor we don't need the intermediate step.
,
Feb 8 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by fsamuel@google.com
, Sep 13 2017