Much as I hate to say this, but if all major JS platforms support some harmless feature, cross-browser web content will come to depend on that feature. In that case, we are better off doing the work to codify an agreed common behavior for that feature, rather than have all implementors guess separately how to best be compatible with what other implementors are guessing. Remember block nested functions as a cautionary tale.
I hope we keep __defineGetter__ etc out of the cross browser web. I had hoped we would keep __proto__ out to no avail. If __defineGetter__ etc becomes part of the cross-browser de facto platform, TC39 should make it de jure. Fortunately, these are easy to shim on any ES5 platform of course. SES already does so < https://code.google.com/p/google-caja/source/browse/trunk/src/com/google/caja/ses/startSES.js#329>. If we do codify these, we should probably follow the logic of this trivial shim. On Tue, May 7, 2013 at 7:21 AM, Dean Landolt <d...@deanlandolt.com> wrote: > > > > On Tue, May 7, 2013 at 10:13 AM, Rick Waldron <waldron.r...@gmail.com>wrote: > >> >> On May 7, 2013 3:49 AM, "David Bruant" <bruan...@gmail.com> wrote: >> > >> > Hi, >> > >> > The latest rumors [1] suggest that __defineGetter__ will be in IE11. >> >> Of course to benefit platform compatibility, but that doesn't mean ES6 >> (or ES.any) will standardize an obsolete feature alongside its superior >> replacement. ;) >> > > So there's no need to standardize __proto__ then, eh? ;) > > </troll> > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss > > -- Cheers, --MarkM
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
