On Nov 10, 2012, at 12:14 PM, John Bauman <email@example.com> wrote:
preserveDrawingBuffer doesn't have to apply here. Today it applies to frame-to-frame preservation. But I think you've hit on the salient issue. If I create a context, not associated with a canvas, render to it, then associate it with a canvas, what happens? I can imagine implementations where you'd need to modify the drawing buffer once you know what canvas it will display to. But that's probably fine. Worst case you'd have to create a new drawing buffer when you attach to the canvas and copy the old drawing buffer to it.
I could imagine giving control over whether or not you want this behavior. But if we did that, I think it would be better to have a separate flag, "preserveDrawingBufferOnAttach" or something like that. There may be different criteria (and performance implications) for each case.