In order to pull the display compositor out of the browser process, we need to remove direct access to SurfaceManager among other things. We should identify how SurfaceManager is used today and wrap all accesses to SurfaceManager instead of having a "GetSurfaceManager()" accessor. I think this primarily means ui::ContextFactory should not have a GetSurfaceManager().
Maybe we can replace those with individual methods that delegate to calls on SurfaceManager methods?
Comment 1 by enne@chromium.org
, Oct 20 2016