Yeah, I already know. Apparently, google led both of us to the same
document!
My mail to Phil:
Oh, cool. According to Laszlo-Dev pipermail, you were just four
seconds faster than me when mailing Tucker about
"http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx";!
:-)
-André
A German IT-News webpage reported yesterday about the ECMAScript 4
discussion between MS- and Mozilla-guys
(http://golem.de/0711/55802.html). The article itself won't be that
interesting for you, except you can speak German,
but the editor linked also to the relevant MS- resp. Mozilla-blogs:
http://blogs.msdn.com/ie/archive/2007/10/30/ecmascript-3-and-beyond.aspx
http://blogs.msdn.com/cwilso/archive/2007/10/31/what-i-think-about-es4.aspx
and:
http://weblogs.mozillazine.org/roadmap/archives/2007/10/open_letter_to_chris_wilson.html
On 11/3/2007 1:16 PM, P T Withington wrote:
You and Phil found the same reference, minutes apart.
This post is viewed by some as an attempt by MS to derail the ES4 effort.
On 2007-11-02, at 19:25 EDT, André Bargull wrote:
Found this page on the web:
http://blogs.msdn.com/jscript/archive/2007/10/29/ecmascript-3-and-beyond.aspx
Quote:
"[...]Did you know that Custom properties that shadow [[DontEnum]]
properties on Object.prototype are not enumerated using for-in in
IE?[...]"
This is the problem. In IE6, 'toString' will not be enumerated,
even if it is an explicit property in an Object:
lzx> for (var k in {foo: 1, toSTring: 2}) Debug.write(k)
foo
toSTring
lzx> for (var k in {foo: 1, toString: 2}) Debug.write(k)
foo
lzx>
