W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2005

[whatwg] Canvas element - Keep It Simple

From: Jim Ley <jim.ley@gmail.com>
Date: Sun, 24 Apr 2005 17:42:31 +0100
Message-ID: <851c8d31050424094238388b24@mail.gmail.com>
On 4/24/05, Kornel Lesinski <kornel at ldreams.net> wrote:
> On Sun, 24 Apr 2005 16:14:29 +0100, Jim Ley <jim.ley at gmail.com> wrote:
> Drawable <img> is pretty easy to implement (change to internal bitmap),

So the proposal to have img alone switch to drawable seems a good one.
 The WHAT-WG members have previously said that new elements are a bad
idea as they're more complicated to implement - re-using image seems a
good option.  Especially as it would give us the ability to use the
image itself as a background - and to provide fallback support for the
user.

Look at google maps, it draws on top of img elements, adding in extra
canvas elements would seem to be highly redundant?

> > The existence of an HTMLCanvasElement prototype is not standard
> > currently
> 
> It's in current draft, with width/height properties and getContext method.

Could you point to where?  Or was I not clear enough about talking
about the _prototype_ that's the thing that is not currently specified
and I believe is hugely unwarranted.

[Prototypes]
> But such coupling is already there for every current form element.
> Prototypes are required by ECMA script already.

Could you point me to the part of the specification?  Because by my
reading of the ECMA spec prototypes are not required on host objects
such as the DOM in a webbrowser.

Jim.
Received on Sunday, 24 April 2005 09:42:31 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:22 UTC