On Tue, Sep 4, 2012 at 10:53 AM, Boris Zbarsky <[email protected]> wrote:
> On 9/4/12 12:43 PM, Boris Zbarsky wrote: > >> 1) Have a way for pages to opt in to software rendering. >> 2) Opt canvases in to software rendering via some sort of heuristic >> (e.g. software by default until there has been drawing to it for >> several event loop iterations, or whatever). >> 3) Have a way for pages to opt in to having snapshots taken. >> 4) Auto-snapshot based on some heuristics. >> 5) Save command stream. >> 6) Have a way for pages to explicitly snapshot a canvas. >> 7) Require opt in for hardware accelerated rendering. >> >> Any others? >> > > Ms2ger points out (without endorsing) that there's an: > > 8) Have every author who wants their canvas to stick around call > toDataURL() and stick the result in an <img src>. > And then the browser presumably uses the img to regenerate the canvas on a lost context? Why not just give developers a callback and let them restore the canvas as they see fit? david > > > -Boris >
