W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2012

Re: [whatwg] Hardware accelerated canvas

From: David Geary <david.mark.geary@gmail.com>
Date: Tue, 4 Sep 2012 11:07:05 -0600
Message-ID: <CA+44znhcYhbKpVtK8_TYBHMqBWf2VobGZeT-+gpntCQy+3DAfQ@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: whatwg@lists.whatwg.org
On Tue, Sep 4, 2012 at 10:53 AM, Boris Zbarsky <bzbarsky@mit.edu> 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
>
Received on Tuesday, 4 September 2012 17:07:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:45 UTC