Currently the BlimpCompositor is the root compositor that draws to the cc::Display and maintains it own cc::Surfaces system.
This will not be possible when Blimp is embedded into Chrome, since Chrome has the Surfaces system and the UI compositor is the parent/root compositor that owns the Display. As a first step, make the Blimp compositing code share its output with the embedder using a cc::SurfaceLayer and put up a small Browser compositor in the app to provide the same functionalities that Chrome is expected to provide.
Comment 1 by bugdroid1@chromium.org
, Aug 25 2016