The Ember core team is incredibly willing to work with browser developers to make sure whatever aspects of future prototypes we polyfill remain up-to-date with the official current versions of spec and planned releases.
This might take a bit of planning/coordination because we're on a 6-week stable release schedule, so advance notice of native implementation of anything on a core type lets us prioritize getting these fixes in. As an aside, polyfill prototype extensions are an optional feature of Ember.js that developers can opt out of (if they choose). It is enabled by default based on community feedback about how commonly people choose to opt in: nothing in the framework itself relies on the presence of these polyfilled behaviors (although individual applications may be written to expect it). On Wednesday, October 1, 2014 5:32:00 PM UTC-4, Mike Taylor wrote: > On 10/1/14, 11:52, Till Schneidereit wrote: > > > Unfortunately, it turns out that Array.prototype.contains breaks the web. > > > Or, the MooTools-using parts of the web, at least. > > > > It looks like apps using Ember.js are affected as well: > > <https://github.com/emberjs/ember.js/issues/5670> > > > > -- > > Mike Taylor > > Web Compat, Mozilla _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
