Description* For Chrome 44 <https://github.com/google/caja/issues/1967>, avoid
doing "O[P] = O[P]" in the case where it would be a noop by ES3
rules, which seems to be sufficient for the issue.
* Found while testing: markFunc did nothing if the function was
already marked. Since the Error subclass constructors now inherit
from the Error constructor per ES6 (and in Chrome), this would cause
the subclasses to not get new___ configured, so 'new EvalError(...)'
would act as 'new Error(...)'. The new___ property now uses the
"o.new___ === o" pattern to avoid being seen as inherited.
@ fbbe498f106d5a41ce337dfc10ad50a8b8441245
Patch Set 1 #
Total comments: 9
Patch Set 2 : ES5/3 compatibility fixes for native accessor properties and Error inheritance. #MessagesTotal messages: 10
|