Comment #19 on issue 164 by charles.kendrick: Wrong order in Object
properties interation
http://code.google.com/p/v8/issues/detail?id=164
@erig I mentioned the next ECMA standard merely as an aside. Certainly,
that's a
separate discussion.
To be very clear, I'm arguing that this problem should be fixed *now* in
Chrome,
without waiting for the ECMA body to release a new version of the standard,
because:
1. it's the existing de-facto standard among all browsers that have ever had
significant market share, dating back 12 years or more
2. because of this problem, Chrome fails compatibility with many, many
existing
websites and applications
3. if Chrome persists in this behavior and various JavaScript platforms
eventually
implement Chrome-specific workarounds, those sites and applications will be
slower in
Chrome, no matter what score Chrome gets in synthetic speed tests where
this problem
doesn't arise.
This issue keeps being filed, and marked as duplicate, and filed again and
discussed
again. Scores of people, in aggregate, have starred the various versions
of the bug.
People maintaining large websites are wondering whether to add
Chrome-specific code,
and platform companies are wondering whether to add silly Chrome-specific
APIs like
sortPropertiesForChrome or chromeExplicitPropertyOrder, and then ask their
customers
to update their applications and sites..
How about we avoid the whole mess and just fix it? :)
--
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
