Good context. I didn't know that they had b0rked bind() as well ;-) I feel like there's as PSA we should write over on webplatform.org for library authors about how to not be future hostile.
On Fri, Oct 12, 2012 at 3:26 PM, Geoffrey Sneddon <gsned...@opera.com>wrote: > 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. > > -- > Geoffrey Sneddon — Opera Software > <http://gsnedders.com> > <http://opera.com> > > ______________________________**_________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss> >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
