Status: New Owner: ---- New issue 715 by teamwenger: object index out of order http://code.google.com/p/v8/issues/detail?id=715
All major browsers maintain index order by order of insertion except chrome (even numeric indexes). There are many duplicate reports on this, but it seems the issue has not been pushed enough. I have yet to read a decent reason to not fix this bug. As a developer, I care more about actual performance in the wild rather than speed tests in a vacuum. Take for instance a website that has reason to care about the order of indexes in an object because of numeric primary keys from a db. For every other browser, the site works as intended. For chrome, it fails on this point. The apparent solution to said problem is to add non-numeric characters to the index and then remove those characters later when actually needing to use the numeric index value. It appears that not only would chrome be a cause of countless meaningless hours of "fixes", but would be slower than others browsers due to this junking and unjunking of indexes. This seems like it would hinder performance and reusability of code. For my sites at least, I have to alter my API and UI quite substantially if I want to support Chrome. I have read in related issues that its bad practice to rely on the order of indexes. Thats new to me, because until now it was in fact very useful. Again, I have yet to read a decent reason why not to fix this bug. Please provide a good reason that deals with reality and real websites. A standard that does not conform to reality is no standard at all. So dont hide behind that. If Im wrong, then Ill happily conform to the new reality, but if not, then Chrome needs to conform to the existing reality before I support it. -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
