On 2011/08/30 08:01:24, Jakob wrote:
The patch itself LGTM.
I don't have any data or experience regarding whether this would "break the
web"
or not. Generally I think we should try to follow the latest ES spec.
How about putting this change into a custom Chromium build and running it through layout tests and some manual browsing?
The current Firefox 6 has still the old behavior, so I would be very careful about such a change. Perhaps we should enable the new behavior only when a related flag has been set and/or in strict mode. I am not really sure how we handle such backwards compatibility breaking changes normally... http://codereview.chromium.org/7792031/ -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
