W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2008

[whatwg] Callback driven initialization of canvas

From: Philipp Serafin <phil127@gmail.com>
Date: Wed, 22 Oct 2008 16:09:05 +0200
Message-ID: <f042876c0810220709g7204bf07nc88a58676460f621@mail.gmail.com>
On Wed, Oct 22, 2008 at 2:07 PM, Fabien Meghazi <agr at amigrave.com> wrote:
> The goal would not be to completely forbid canvas but to block it by
> default while allowing the user to activate it when he wants to.

This is a nice feature to have, but the problem is, would it work in
reality? It works for Flash, since it most of the flash scripting is
loaded together with the applet. However, Canvas elements will
probably interface much more with the rest of the page than Flash
applets. I believe many applications would need large amounts of
additional code to handle graceful degrading *and* late loading of
such elements, even with callbacks. Would many web authors use this

Then again, maybe the onLoad event would be a good place for such a callback?
Received on Wednesday, 22 October 2008 07:09:05 UTC

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