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

Re: [whatwg] Hardware accelerated canvas

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 4 Sep 2012 10:12:14 -0700
Message-ID: <CAAWBYDAa538-D52monZfjkbWbB+iLq+HspX+coGJ+ZfUh0Zwdg@mail.gmail.com>
To: David Geary <david.mark.geary@gmail.com>
Cc: whatwg@lists.whatwg.org, Boris Zbarsky <bzbarsky@mit.edu>
On Tue, Sep 4, 2012 at 10:07 AM, David Geary <david.mark.geary@gmail.com> wrote:
> On Tue, Sep 4, 2012 at 10:53 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> 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?

No, the author just uses the <img> in their page instead.  The
<canvas> is only used in JS to generate the image, and is never put
into the document at all.

And again, the reason that "just give them a contextloss event" is bad
is because most people simply won't do it.  It doesn't make any sense!
 The browser just... forgets about your image, which it was displaying
fine just a second ago?

~TJ
Received on Tuesday, 4 September 2012 17:13:06 UTC

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