This is a normative change in the ECMA-262 spec. See: https://github.com/tc39/ecma262/commit/22de374 The issue noted here has been fixed in the same way that we previously worked around it. Update the spec notes to match.