Move FrameGenerator to components/viz/host and use in content too |
|||||
Issue descriptionWe want to move to a world where viz::Displays are no longer tied to ui::Compositors. ui::Compositor is an unprivileged "client library". FrameGenerator is responsible for: 1. Submitting a top level CompositorFrame that embeds the window manager/browser UI. This means ash or browser UI are just another peer client in the compositing system. 2. Display resolution changes. 3. High contrast mode. 4. Hit test region visualizations. 5. Software mirroring mode. The implications to content is "PerCompositorData" goes away in GpuProcessTransportFactory and other ContextFactory implementations. FrameGenerator gets a "RootCompositorFrameSinkImpl" on the viz service side. This corresponds to calling HostFrameSinkManager::CreateRootCompositorFrameSink. The end state is all OutputSurface code lives only in components/viz/service/display_embedder. This is really a large umbrella bug that captures all this work. This may turn into more subbugs.
,
Aug 26 2017
,
Aug 26 2017
,
Feb 9 2018
,
May 25 2018
Bumping this...maybe this makes sense to do for software mirroring mode on Chrome OS.
,
Aug 2
Is this necessary? Or only nice to have?
,
Aug 2
FrameGenerator no longer exists. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by fsam...@chromium.org
, Aug 26 2017Cc: enne@chromium.org
Status: Available (was: Untriaged)