On Mon, Dec 6, 2010 at 4:45 PM, Gregg Tavares (wrk) <email@example.com> wrote:Hmm, it looks like the "Khronos Working Draft" banner might have
> Should these extensions be marked as "draft" given that not even the WebGL
> spec is official yet?
gotten lost during recent CSS changes. Vlad, could we add that back?
(Or did I miss it during the initial commit?)
It's not completely trivial and would double the number of code paths
> Also, is there any particular reason the specs limit texImage2D and
> texSubImage2D to only using ArrayBufferView? Given all the conversion that
> happens already for texImage2D with img/video/canvas it seems like it would
> be really simple for implementations to support conversions to float and
> half float like they already convert to 4_4_4_4, 5_6_5 and 5_5_5_1
in some areas. Also, until browsers have built-in support for high
dynamic range image formats, these conversions will just waste space.
For these reasons I think this should be left to a future revision of
> On Mon, Dec 6, 2010 at 10:45 AM, Kenneth Russell <firstname.lastname@example.org> wrote:
>> The WebGL working group is pleased to announce the availability of the
>> WebGL extension registry. The preliminary URL is:
>> This URL is likely to change in the coming weeks. A link to the
>> registry has been added to the references section of the
>> specification, and that link will be kept up to date.
>> OES_texture_float is close to being implemented in WebKit, and we'll
>> post to the list once it is.
>> Specifications for a few more extensions (OES_depth24,
>> OES_standard_derivatives, ...) are planned; see comments in the HTML
>> for the extension registry.
>> You are currently subscribed to email@example.com.
>> To unsubscribe, send an email to firstname.lastname@example.org with
>> the following command in the body of your email: