On Mar 16, 10:45 pm, RobG <[email protected]> wrote: > On Mar 16, 10:42 pm, Alex <[email protected]> wrote: > > 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. >
I'm more than a little stunned by the irony of an author of a library specifically championed as removing the differences in behaviour between browsers complaining about a difference in behaviour between browsers. ...and basing some key parts of his code on the idea that a structure with no explicit ordering or specification of an implied order should maintain some specific order. (Hmm. This is a bit snarky for my first post to this group. I'll go and introduce myself on the intros thread.) -- 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]
