[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Public WebGL] Feedback from HTML5 WG on WebGL | [Fwd: Re: WebGL | The 3D Canvas Context for HTML]
Since our release yesterday, we've got some feedback from the W3C HTML5
Listserv. Most of the WHATWG post on the HTML5 listserv at W3C, which
has the advantage of attracting Microsoft participation. The W3C HTML5
listserv is archived publicly here:
--- Begin Message ---
On Thu, 10 Dec 2009 23:47:07 +0100, Arun Ranganathan <firstname.lastname@example.org>
- To: email@example.com, "HTML WG" <firstname.lastname@example.org>
- Subject: Re: WebGL | The 3D Canvas Context for HTML
- From: "Anne van Kesteren" <email@example.com>
- Date: Fri, 11 Dec 2009 10:20:47 +0100
- In-reply-to: <4B217A6B.firstname.lastname@example.org>
- Organization: Opera Software ASA
- References: <4B217A6B.email@example.com>
- User-agent: Opera Mail/10.10 (MacIntel)
I've been trying to cut my mailing list subscriptions recently so
hopefully someone can forward this as appropriate.
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
--- End Message ---