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. :)
Many things in MooTools Core depends on itself.
On 13/10/12 11:47, David Bruant wrote:
2012/10/12 Geoffrey Sneddongsned...@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
2012/10/12 Geoffrey Sneddon gsned...@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
2012/10/12 Alex Russell slightly...@google.com
I feel like there's as PSA we should write over on webplatform.org for
library authors about how to not be future hostile.
Some context for those who wouldn't have followed.
The W3C, major (western?) browser makers, Nokia, Facebook, HP, Adobe
On Sat, Oct 13, 2012 at 12:34 PM, David Bruant bruan...@gmail.com wrote:
2012/10/12 Alex Russell slightly...@google.com
I feel like there's as PSA we should write over on webplatform.org for
library authors about how to not be future hostile.
Some context for those who wouldn't have
2012/10/13 Alex Russell slightly...@google.com
On Sat, Oct 13, 2012 at 12:34 PM, David Bruant bruan...@gmail.com wrote:
Since it's in such an early stage and it's not really well-known and
well-established, is webplatform.org the right place to do a PSA as you
suggest?
Do you have a
Hi,
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.
David
[1]
Hello,
I've found the issue in mootools-core [1].
[1] https://github.com/mootools/mootools-core/issues/2402
Regards,
Yusuke Suzuki
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
It's unclear what we should do here. Their test-and-install mechanism was
overly optimistic and therefore future hostile. It looks as though outreach
is happening and they're fixing their library and aligning with ES6 in
future releases.
My suggestion is to wait-and-see what browser vendor
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
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.comwrote:
On 12/10/12 14:50, David
On Fri, Oct 12, 2012 at 10:09 AM, Alex Russell slightly...@google.comwrote:
It's unclear what we should do here. Their test-and-install mechanism was
overly optimistic and therefore future hostile. It looks as though outreach
is happening and they're fixing their library and aligning with ES6
12 matches
Mail list logo
