W3C home > Mailing lists > Public > public-html@w3.org > December 2009

Re: WebGL | The 3D Canvas Context for HTML

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 11 Dec 2009 10:20:47 +0100
To: arun@mozilla.com, "HTML WG" <public-html@w3.org>
Message-ID: <op.u4rn8xys64w2qv@anne-van-kesterens-macbook.local>
On Thu, 10 Dec 2009 23:47:07 +0100, Arun Ranganathan <arun@mozilla.com>  
wrote:
> [...]

I've been trying to cut my mailing list subscriptions recently so  
hopefully someone can forward this as appropriate.

https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html

The draft appears to use outdated Web IDL syntax. It also uses features,  
e.g. NameDeleter that are controversial with TC39 so you may want to  
reconsider using those.

It also seems that a bunch of the new objects introduced should really be  
part of ECMAScript instead. E.g. all the new typed array interfaces.

Some of the typedefs are scoped to WebGLRenderingContext but are in fact  
used all over the place.

Also, why is it WebGLRenderingContext and not CanvasRenderingContextWebGL  
which would be more consistent with the existing CanvasRenderingContext2D?

It does not seem to be defined when the event defined at the end of the  
specification is actually dispatched. The name of the event is also not  
defined, just the interface it implements. Also, if more than one resource  
is lost, which one does "resource" return? And why do you need the context  
attribute? Isn't it already clear that the event is for the WebGL context?


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Friday, 11 December 2009 09:21:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:55 UTC