Comment #87 on issue 164 by [email protected]: Wrong order in Object properties interation
http://code.google.com/p/v8/issues/detail?id=164
But the point is, up to the point where Chrome decided to change behaviour, all other major browsers did it that way. So the initial decicion was in my opinion not the best one to be made: changing something that was working the same way on every major browser (even Chrome did it that way before) seemingly purely for better synthetic benchmark score. And sad thing is, Opera and IE seem to be hopping on the same wagon with latest releases. And you know the saddest part, I tested IE platform preview 3, which still had the "loop in order of definition" behaviour and the looping seemed to be almost 2 times faster than Chrome, which does reordering on object (for performance reasons...).
But yes, now when other browsers are also jumping on same wagon of benchmarks over logic and compatibility, the only way to force browsers back to previous behaviour is to get this into ecmascript ASAP through their community feedback.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
