Comment #11 on issue 2605 by soapergem: javascript associative array's 'numerical' keys are not in order http://code.google.com/p/chromium/issues/detail?id=2605
jhaas: That's a terrible cop-out answer. There are plenty of things I could come up with that are not part of the spec, but are done anyway for consistency with other browsers. For example, where in any spec is there mention of "innerHTML"? The fact is that every other browser out there maintains some order for the sake of convenience, so by doing things differently here Chrome becomes the problem child to which we have to accommodate. And don't forget: ordered objects are a subset of unordered objects-- in other words, given any ordered object, you can claim that it is unordered, but not the other way around. So you could order things and still "claim" that they're unordered and up to spec. And then everyone would be happy. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
