Mootools and String.prototype.contains

Geoffrey Sneddon gsneddon at opera.com
Mon Oct 15 13:49:41 PDT 2012


On 13/10/12 11:47, David Bruant wrote:
> 2012/10/12 Geoffrey Sneddon<gsneddon at opera.com>
>
>> >On 12/10/12 14:50, David Bruant wrote:
>> >
>>> >>I was looking at Bugzilla and came across two bugs [1] [2] related to
>>> >>Mootools-based (only Mootools 1.2-) websites being broken by the inclusion
>>> >>of String.prototype.contains in SpiderMonkey.
>>> >>I don't think it's been brought to the list yet, though I think it's
>>> >>relevant.
>>> >>
>> >
>> >Given there were similar issues with Function.prototype.bind in the same
>> >release of Mootools, I'm inclined to let it slide: Mootools 1.2 already
>> >broke given ES5, and that was pushed through regardless.
> By intuition, I'd say there is much more code with mystring.contains than
> uses of myfunction.bind and so pushing .contains may have more impact than
> .bind did.
> But that's just an intuition.

My memory was Mootools itself depended on bind, so it was significantly 
more that broke, thus my conclusion. Someone (probably me!) should check 
what it was that actually broke, exactly. :)

-- 
Geoffrey Sneddon — Opera Software
<http://gsnedders.com>
<http://opera.com>


More information about the es-discuss mailing list