Having a non-enumerable Array.prototype.contains may not be web-compatible
john.david.dalton at gmail.com
Tue Sep 30 12:46:44 PDT 2014
MooTools breaking because of additions/changes is not a new thing. It has
been broken in the past by things like Function#bind, String#contains, &
Moz removing document.getBoxObjectFor.
Its activity has slowed overall though there is an effort to re-energize
core contributions. Their core has put effort towards another project,
Prime, which does not augment native prototypes.
On Tue, Sep 30, 2014 at 12:45 PM, Andrea Giammarchi <
andrea.giammarchi at gmail.com> wrote:
> "the current state of the web" ... with all due respect for that library,
> it's been years since I've heard anything about it.
> It's also common on the old web to loop over Arrays via `for/in` to avoid
> checks for sparse indexes through the entire length ... so making anything
> enumerable in that native prototype would break something else too form
> days where `getOwnPropertyNames` was unknown.
> long story short: I definitively +1 what Michał Wadas already said, it's
> already patched and people must update software anyway due security
> problems, **patches**, etc etc.
> just my .02
> On Tue, Sep 30, 2014 at 8:18 PM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
>> On 9/30/14, 2:45 PM, Michał Wadas wrote:
>>> Bug in MooTools is not a reason to make any method of Array.prototype
>> I didn't say we need to make it enumerable.
>> I said that given the current state of the web, a web browser cannot ship
>> a non-enumerable method named "contains" on Array.prototype.
>> The options, therefore, are:
>> 1) Make the method enumerable.
>> 2) Name the method something else.
>> 3) Don't ship the method until every site that currently uses the
>> buggy versions of MooTools (which is every site that uses
>> MooTools, since they only fixed it 4 days ago).
>> I'm perfectly fine with option 3, personally. Note that in practice that
>> likely means "never ship it" unless people make some sort of concerted
>> effort to get sites to update their MooTools version.
>> P.S. It may be worth avoiding the method names mootools sets up but
>> doesn't force-copy in the future. Even better would be getting them to fix
>> their code so there are no such method names, of course.
>> es-discuss mailing list
>> es-discuss at mozilla.org
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss