On Tue, May 6, 2014 at 2:00 PM, Gabriele Svelto <gsve...@mozilla.com> wrote: > On 06/05/2014 14:43, Anne van Kesteren wrote: >> I suppose longer term we can map the older version to the newer >> versions somehow, but that's still an awfully big API surface area to >> maintain. > > The wording of the spec seems to imply that besides the context creation > the API is a superset of WebGL 1.0 [1] so it shouldn't require an > entirely separate API but just extending the existing one. Or am I > missing something? > > [1] «WebGL 2 is backwards compatible with WebGL 1: existing content will > run in WebGL 2 without modification. To access the new behavior provided > in this specification, the content explicitly requests a new context»
It seems I missed something. However, I cannot find where it justifies having a mode switch. If the API is backwards compatible, there should be no need for a mode switch. We've learned twice now that mode switches are a source of pain (quirks mode, "use strict"). It looks like we're about to learn it a third time, unless I'm missing even more. -- http://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
