I wanted to record my conversation with Dana in a bug somewhere before I forget. GpuDisplayCompositorFrameSink, and GpuOffscreenCompositorFrameSink are a bit of a misnomer.
Both are "onscreen" in the sense that their content will be displayed on screen at some point. What might make more sense is calling the root CompositorFrameSink that holds a cc::Display, GpuRootCompositorFrameSink, and call the child GpuCompositorFrameSink.
GpuRootCompositorFrameSink != a derived class of GpuCompositorFrameSink though because the Root holds an associated interface to MojoCompositorFrameSink.
That's OK, DisplayCompositor can simply hold a map to MojoCompositorFrameSink*.
Comment 1 by fsam...@chromium.org
, Feb 22 2017Status: Assigned (was: Untriaged)