Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-23 Thread Mike Taylor
On 10/17/14, 16:13, Jeff Walden wrote: On 10/17/2014 01:53 PM, Erik Arvidsson wrote: [1] Microsoft Outlook Calendar web app (part of Exchange Outlook Web Access) Microsoft could ship a fix in a point release, right? They surely already provide security patches that admins must install anyway

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-22 Thread Brendan Eich
Katelyn Gadd wrote: Has the C# approach to namespace extension been considered at all? Yes. ES4 has namespaces, after Common Lisp symbol packages. Scoped object extensions were proposed four years ago for ES6, but foundered on the same thing that killed ES4 namespaces: adding a second lookup

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-22 Thread Katelyn Gadd
Has the C# approach to namespace extension been considered at all? With extension methods (one of the foundational primitives used to implement their LINQ querying system) they address this by making extension namespaces 'opt-in' - extension methods are only 'available' on an object if you've impor

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-20 Thread Andy Wingo
On Sun 19 Oct 2014 02:46, Fabrício Matté writes: > But in reality, many developers simply won't follow the best practices, > and as Domenic said, browser vendors don't want to ship changes that > break existing code. > > Looks like we have reached a stalemate, and I believe this is something > th

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-19 Thread Fabrício Matté
@Benjamin Not sure if I understand what you mean. If standards don't "dictate", then how are we supposed to expect interoperable implementations? By "impossible" I suspect you mean something that browser vendors should never do. I understand back-compatibility with the Web is a must for browser

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-19 Thread Benjamin Gruenbaum
Just as a note - I think that if we learned anything in this regard it's that standards should guide and not dictate. It׳s rather impossible to break reasonable user level code and I don't think it's reasonable to expect developers to be fortune tellers :) (I like the idea though) > On Oct 19

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-18 Thread Fabrício Matté
Here is a related Twitter discussion: https://twitter.com/domenic/status/523202298466418688 To highlight the main points: > Domenic Denicola claims that extending built-in prototypes is not web-compatible. Indeed, if we consider all possible corner-cases and ignore best practices (which is often

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-17 Thread Erik Arvidsson
Here is some more info. http://windowssystemspecialist.blogspot.com/2014/10/fixing-blank-calendar-with-chrome-38.html (This blog post would have been useful when we tracked down what caused OWA to fail.) On Fri, Oct 17, 2014 at 5:13 PM, Jeff Walden wrote: > On 10/17/2014 01:53 PM, Erik Arvidss

Re: Array.prototype.values is not web compat (even with unscopables)

2014-10-17 Thread Jeff Walden
On 10/17/2014 01:53 PM, Erik Arvidsson wrote: > [1] Microsoft Outlook Calendar web app (part of Exchange Outlook Web Access) Microsoft could ship a fix in a point release, right? They surely already provide security patches that admins must install anyway, if they want to keep their users (and

Array.prototype.values is not web compat (even with unscopables)

2014-10-17 Thread Erik Arvidsson
We learnt this the hard way. There are pages [1] out there that check if `"values" in object` and now that ends up being true for Array instances. [1] Microsoft Outlook Calendar web app (part of Exchange Outlook Web Access) -- erik ___ es-discuss mail