>-----Original Message----- >From: Tobie Langel [mailto:[email protected]] >... >Some of the challenges faced by the Prototype JavaScript Framework >involve certain methods specified in ES 3.1 (notably the new >Array.prototype methods) which were implemented in Prototype prior to >their specification. Doing so causes significant backward- >compatibility issues and is best avoided. >
I'd be interested in more details on how the new Array.prototype methods cause you problems. With only one or two exception, they are the same as the Mozilla "Array extra" methods so you must already have to deal with the possibly that they are present in some browsers. The new methods are all writable so if somebody wants to unconditionally install their own replacements they can. We are certainly trying to minimize negative impacts of these sorts of additions so if our mitigations are not sufficient it would be very useful to understand why. Would it be useful if there was a way to determine whether nor not a function was "built-in"? Allen _______________________________________________ Es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
