.entries() vs. the web
erik.arvidsson at gmail.com
Mon Jun 16 16:10:54 PDT 2014
That is why you need to implement @unscopables too.
On Jun 16, 2014 7:08 PM, "Oliver Hunt" <oliver at apple.com> wrote:
> It turns out there are a number of sites (such as mobile.twitter.com)
> that are property detecting .entries on objects, and that means that
> they're breaking when Array.prototype.entries is provided.
> We're removing it from JSC now, until we can find a way to expose it
> without causing site breakage, although this does seem like fixing it would
> require bringing back the awful "pretend that you're undefined" horror.
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss