Comment #85 on issue 164 by [email protected]: Wrong order in Object properties interation
http://code.google.com/p/v8/issues/detail?id=164
Well, it seems to me that before all those synthetic benchmark races, all browsers worked predictably, even though ecmascript spec did not actually define anything about ordering and looping. Then the javascript race started (with chrome in 2008 as seen from the start date of this bug) and chrome guys decided to speed up their js engine and dropped the "ordering as added" feature because it was not actually defined in ecmascript rules by that time. After that Opera dropped the reordering thing from 10.5 and if I'm correct the latest IE beta and platform preview have dropped that feature too.
So it all started with Chrome guys dropping a feature that has been around a long time and everyone expects to work, just to gain some advantage in synthetic benchmarks. And now everyone except firefox and safari is following the lead and breaking tons of webpages. I was starting to suggest people use chrome because of it's startup speed and nice html5 rendering but after seeing this bug in action on many pages that used to work normally, I'm suggesting people to use firefox. Reasoning is: I cannot fix pages that I don't own plus IE 6+7+8 combo with firefox hold big percentage of browser share, so it's not especially important for medium sized webpages if some users have some minor non-critical issues.
Instead of using any code workarounds, best workaround is to use another browser that does not try to overdo itself with synthetic benchmarks scores but still retains some logic. Sorry Chrome...
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
