Remove callerRealm from HostEnsureCanCompileStrings

[antosart]

This PR removes the parameter callerRealm from HostEnsureCanCompileStrings. The parameter was sent to EnsureCSPDoesNotBlockStringCompilation in CSP, which however does not use that parameter (the parameter is being removed there, too, see w3c/webappsec-csp#541).

This change is a no-op, so I believe the following does not apply.

• At least two implementers are interested (and none opposed):
  • …
  • …
• Tests are written and can be reviewed and commented upon at:
  • …
• Implementation bugs are filed:
  • Chrome: …
  • Firefox: …
  • Safari: …
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …

(See WHATWG Working Mode: Changes for more details.)

---

/index.html ( diff )
/timers-and-user-prompts.html ( diff )
/webappapis.html ( diff )

[antosart]

The companion PR on ECMAScript is tc39/ecma262#2670.

[domenic]

Tagging "do not merge yet" until the 262 PR is merged.

(Note, if they don't want to merge it in 262, then we can adapt this PR to just not pass the second realm to CSP.)

[antosart]

tc39/ecma262#2670 is merged, so we should be good to go here.

In tc39/ecma262#2670 it was suggested to rename calleeRealm into something more neutral, like currentRealm. I have no strong preference here, but I am happy to change this.

[annevk]

Maybe we should call it realm?

The weird thing is that "callee" isn't referring to HostEnsureCanCompileStrings, but rather to the caller of HostEnsureCanCompileStrings.

[antosart]

Makes sense. I renamed it realm.

[annevk]

Thanks @antosart for making the cleanup happen across all these repositories, this is a lot better.