Implement WebGL's commit on the main thread

third_party/WebKit/public/platform/modules/offscreencanvas/offscreen_canvas_surface.mojom

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 module blink.mojom;
 
 import "cc/ipc/compositor_frame.mojom";
+import "cc/ipc/returned_resource.mojom";
 import "cc/ipc/surface_id.mojom";
 import "cc/ipc/surface_sequence.mojom";
 
 interface OffscreenCanvasSurface {
   // TODO(619138): Make creation of surface id Async after implementation
   // change on surface_id generator that makes client side be able to generate
   // unique surface_id.id_namespace alone.
   [Sync]
   GetSurfaceId() => (cc.mojom.SurfaceId surface_id);
 
   Require(cc.mojom.SurfaceId surface_id, cc.mojom.SurfaceSequence sequence);
   Satisfy(cc.mojom.SurfaceSequence sequence);
 };
 
 // This interface is called from either worker or main thread in renderer, but
 // not both for the same OffscreenCanvas instance.
 interface OffscreenCanvasFrameReceiver {
 
+  SetClient(OffscreenCanvasFrameReceiverClient client);
   SubmitCompositorFrame(cc.mojom.SurfaceId surface_id, cc.mojom.CompositorFrame compositor_frame);
 
 };
 
+interface OffscreenCanvasFrameReceiverClient {
+  ReturnResources(array<cc.mojom.ReturnedResource> resources);

[dcheng, 2016/09/14 20:02:19]

Would it make sense for this to be a generic CC mojo interface? It seems like we
already have SurfaceClient and CompositorFrameSinkClient with the exact same
interface.

[danakj, 2016/09/14 20:07:56]

Not sure if this is helpful but this here *is* a CompositorFrameSinkClient, so
maybe it should use that interface? Maybe it should use CompositorFrameSink too,
not sure if this was considered or is possible.

[xidachen, 2016/09/15 15:56:28]

+Fady: WDYT?

+};
+