On Mar 16, 10:42 pm, Alex <[email protected]> wrote: > Thank you very much for this. > > This seems to be the most "logical" explanation for "for / in " > construct. > > What I found is that Chrome does not (did not) follow that rule.
Chrome is compliant with ES 3 and ES 5 in that regard. There is no reason to believe any browser will return object properties in the order they were added, both specifications quite clearly state that. > Seehttp://code.google.com/p/chromium/issues/detail?id=883 That thread shows some very ignorant and arrogant attitudes. -- Rob -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
