66435 2011-08-17 17:08:26 -0700 [chromium] Remove LayerRendererChromium references from Canvas2DLayerChromium 2011-08-23 17:46:22 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 66743 66430 1 enne webkit-unassigned enne husky jamesr nduca oldest_to_newest 452746 0 enne 2011-08-17 17:08:26 -0700 LayerRendererChromium is a compositor thread-side class, so Canvas(2D)LayerChromium should not have access to it, except during updateCompositorResources. The DrawingBuffer creation and destruction and its interaction with the LRC are probably the largest problems here. The removal and addition of child contexts will have to be deferred until the next commit and stored somewhere (CCLayerTreeHost?). 452749 1 enne 2011-08-17 17:14:19 -0700 Also, maybe setDrawingBuffer could be removed, as it doesn't seem to be used anywhere except to clear the drawing buffer in some other class's destructor. 453153 2 jamesr 2011-08-18 11:07:42 -0700 I don't think we actually need the child context stuff any more, that was for some latching code that's redundant now. I'll confirm that with Bates. 455884 3 jamesr 2011-08-23 17:46:22 -0700 I think we're good here now, DrawingBuffer only touches the canvas context (not the compositor context) and there's no child context stuff any more. Marking as fixed.