Comment #16 on issue 164 by soham.mehta: Wrong order in Object properties
interation
http://code.google.com/p/v8/issues/detail?id=164
It is easy to say WorkingAsInteded. But having everyone else update their
code (in plenty of cases, lot of legacy code), is not a good idea. If we
don't fix this, then either we're
hindering adoption of chrome, or we're having a lot of people do a lot more
work than what is practical.
It can have unintended consequences e.g. screwing up the order of featured
items, where payments go by the order of placements. As an example, check
the order of services listed at
http://www.box.net/services/featured . Use [email protected]/test .
Latest versions of all browsers agree on the order, except for chrome.
We totally understand that ECMA spec does not mandate the order, but this
is not really an engineering question - at least not anymore. This is a
question of playing well together with
other browsers and being properly backwards compatible, so to speak.
It is an unfortunate situation, but I'm sure this is not the first one and
not as hard to work around/live with. At the least, we can provide a
chrome-specific directive that can change
interpretation of array order (not a good solution, but an example). Also,
is there a benchmark on how much memory overhead we're talking about?
--
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
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
