Summary: | %ThrowTypeError% is defined more than once per realm | ||
---|---|---|---|
Product: | WebKit | Reporter: | Richard Gibson <richard.gibson> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | ashvayka, mark.lam, saam, webkit-bug-importer, ysuzuki |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Richard Gibson
2022-04-26 18:12:27 PDT
Nice catch! "arguments `callee` getter" and "arguments `callee` setter" should have the same %ThrowTypeError%, but for the other cases, we are currently following to https://github.com/claudepache/es-legacy-function-reflection/blob/master/spec.md Are you saying that you conform with a Stage 1 proposal rather than the published specification? If so, why? (In reply to Richard Gibson from comment #4) > Are you saying that you conform with a Stage 1 proposal rather than the > published specification? If so, why? Yes, we implement the Stage 1 proposal almost in full (except for cross-realm leakage which we still allow). I've determined two benefits in aligning with SM and moving accessors to Function.prototype: * that greatly simplified our JSFunction overrides; * a userland function with own non-configurable properties was problematic to use as [[ProxyTarget]]. |