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 advocacy can accomplish without either changing the name of contains() in the drafts or removing it. On Fri, Oct 12, 2012 at 3:04 PM, Yusuke Suzuki <utatane....@gmail.com>wrote: > 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 > >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
