Hy

We had a convo about MUS the other day and it came up that we might move raster to be after surface aggregation one day.. which is to say, moving tile manager and layers and stuff.. into the display compositor again.

So enne and I are thinking maybe it's not worth moving the contents of cc/surfaces to display_compositor as that's probably going to be some weird churn.

However all the embedder stuff (things in c/b/compositor/ for the display compositor) should probably continue to become a separate component like display_compositor, and that would just be the embedder of code in cc/surfaces/.

sgtm Marking as WontFix

(The *OutputSurface part of the title still applies though, maybe that's elsewhere?)

Back to available. :-)

Given we want to get rid of OutputSurface now, I'm marking as WontFix.

OutputSurface is going to continue to exist for display compositor (or the functionality inside it).

It's going away for LayerTreeHost.

So.. un-WontFix'd unless I'm misunderstanding.

Reopened then.. Hmm, this bug is a bit ambiguous then. I guess part of this bug is for whoever picks it up to figure out what all the *OutputSurfaces are used for in content/browser/compositor and which can and should move to display_compositor.

All of them can move except the one passed to ui::Compositor.

AKA this one: https://code.google.com/p/chromium/codesearch#chromium/src/content/browser/compositor/gpu_process_transport_factory.cc&l=485

I started looking at this, and it looks like: because of some of the dependencies of content/b/c/*output_surface*, the following also need to move into /components/display_compositor/: ImageTransportFactory (the pure interface), ReflectorTexture, ReflectorImpl, OwnedMailbox. Does that sound OK, or would it be necessary to keep them in content/b/c/?

Hmm, I don't think we want to use the current content/ version of reflector. We also don't want display_compositor to depend on ui/compositor.

Did y'all decide what you want reflector to look like (inside mus or inside the browser)?

Moving OwnedMailbox sounds okay fwiw.

ImageTransportFactory is used throughout content, and is what it is meant for. What pieces of it need to move to display_compositor? I think decoupling c/b/compositor from that interface and using GPTF directly is probably part of the pre-req work here.

re: Reflector: reimplement in terms of Surfaces. The interior details are TBD.