@@unscopeable doesn't work as they are not using |with| The logic is something along the lines of
if (foo.entries) ... It looks like there are paths that objects or arrays may path through, with "entries" being a perfectly reasonable property name in the object case, but now the array case hits the entries property on Array.prototype --Oliver > On Jun 16, 2014, at 4:10 PM, Erik Arvidsson <[email protected]> wrote: > > That is why you need to implement @unscopables too. > > On Jun 16, 2014 7:08 PM, "Oliver Hunt" <[email protected]> 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. > > --Oliver > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
