New issue
Advanced search Search tips

Issue 759308 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 732805



Sign in to add a comment

Move FrameGenerator to components/viz/host and use in content too

Project Member Reported by fsam...@chromium.org, Aug 26 2017

Issue description

We 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.
 
Blocking: 732572 732805
Cc: enne@chromium.org
Status: Available (was: Untriaged)
Labels: -Pri-3 Pri-2
Description: Show this description
Blocking: -732572
Bumping this...maybe this makes sense to do for software mirroring mode on Chrome OS.
Is this necessary? Or only nice to have?
Status: WontFix (was: Available)
FrameGenerator no longer exists.

Sign in to add a comment