Description[string] Fix null handling in MaybeCallFunctionAtSymbol
The spec requires that a null @@split / @@replace symbol is treated exactly the
same as if it were undefined, i.e. execution should move on to the default
implementation instead of throwing a TypeError.
BUG=v8:6313
Review-Url: https://codereview.chromium.org/2845153002
Cr-Commit-Position: refs/heads/master@{#44959}
Committed: https://chromium.googlesource.com/v8/v8/+/281488547744d3341cd9c1d92489696420ee63c1
Patch Set 1 #Patch Set 2 : Clarify comments #
Messages
Total messages: 15 (11 generated)
|