W3C home > Mailing lists > Public > public-gpu@w3.org > July 2017

Re: Minutes for the 2017-06-21 meeting

From: Kenneth Russell <kbr@google.com>
Date: Wed, 5 Jul 2017 20:05:28 -0700
Message-ID: <CAMYvS2eFs8sW0vBj4pV2muwbzYNiqLNJL-qOD3MSb0CqKLEvtQ@mail.gmail.com>
To: Stephen White <steve@adam.com.au>
Cc: Corentin Wallez <cwallez@google.com>, public-gpu@w3.org
On Tue, Jun 27, 2017 at 6:06 PM, Stephen White <steve@adam.com.au> wrote:

> On 28 Jun 2017, at 6:23 am, Corentin Wallez <cwallez@google.com> wrote:
> > As far as I know it is a myth that WebGL code broke because of such
> fixes: all the original WebGL demos still work.
>
> I was referring to the pre 1.0 WebGL code. I remember two incompatible
> changes, and linked to an example in the Github issue.
>

Steve, which Github issue are you referring to? Could you please post a
link?

It's true that some of WebGL's API signatures changed early on, in
incompatible ways. This was problematic because WebGL 1.0 was enabled by
default in browsers under the "experimental-webgl" context type. Since
then, browser implementers have chosen a better staged rollout plan for new
APIs – only enabling them by default when multiple browsers are passing
conformance tests. If the gpuweb implementations follow this convention,
then early adopters will still be able to try things out, but the backward
compatibility guarantee won't be enforced until everyone's ready to provide
it.

-Ken



>
> --
>   steve@adam.com.au
>
>
>
Received on Thursday, 6 July 2017 03:06:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:52:21 UTC