We'd like to use GpuCompositorFrameSink in Chrome (replace OffscreenCanvasCompositorFrameSink, for example) so ideally, it should not depend on DisplayCompositor just yet. This probably means the following:
1. GpuCompositorFrameSink takes in a SurfaceManager directly instead of a DisplayCompsoitor.
2. DisplayCompositor is a GpuCompositorFrameSinkDelegate for OnClientConnectionLost and OnPrivateConnectionLost.
Comment 1 by fsam...@chromium.org
, Jan 22 2017