This is a gently reminder I don't represent my company anyhow in this mailing list but actually I've been working on mobile web here at twitter for 1.5 years how ... thanks for the report, I'll do what I can (already patched, waiting reviews) + I don't think mobile web should block anyhow new standards no matter where I work.
Best Regards On Mon, Jun 16, 2014 at 4:52 PM, Claude Pache <[email protected]> wrote: > Apparently, this problem was already known more than 4 months ago: > > https://bugzilla.mozilla.org/show_bug.cgi?id=924386#c19 > > I guess it specifically affect the mobile web? for it didn't prevent > Firefox to ship `Array.prototype.entries` in v28, released on March 18. > > —Claude > > Le 17 juin 2014 à 01:08, Oliver Hunt <[email protected]> a écrit : > > > 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 >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
