[whatwg] Canvas 2d methods

Ric Hardacre whatwg at cycloid.f9.co.uk
Mon Jul 3 00:53:17 PDT 2006

Ian Hickson wrote:
> On Mon, 3 Jul 2006, Håkon Wium Lie wrote:
>>> Anyway, this is all a straw man -- this isn't the reason that the spec 
>>> doesn't allow this. It doesn't allow this because Safari didn't do it 
>>> this way in the first place, and changing it would likely introduce 
>>> bugs (while still not helping authors for some time anyway).
>> It's still early in the life of the canvas element, and we still have 
>> the luxury of listening to good proposals. We can deal with the minor 
>> problems that arise, and authors down the road will have a more 
>> intuitive syntax. I like the proposal.
> Well as I mentioned, I'm fine with the idea per se, if implementors are 
> willing to change their implementations and fix any resulting bugs, then 
> the spec will follow.

I'm also strongly in favor of this. If only because it seems intuitive
considering that this is the norm for most objects in not just the JS
universe but increasingly others (e.g. C#, and you can even do it with
some objects in VBs) so it's not like we're introducing an alien concept

Ric Hardacre

More information about the whatwg mailing list