Realms Initialization Control

[weizman]

こんにちは TAG-さん!

I'm requesting a TAG review of Realms Initialization Control.

Initialization of same origin realms in an application should be under that application's control.

This proposal describes an opt-in capability to set a script to be loaded first, every time a same origin realm with synchronous access to the main execution environment of the application is created.

The location of the script can be relative or absolute. Secure connection is required. The proposed method for setting the script is a Content Security Policy directive as follows: Content-Security-Policy: "realm-init: /scripts/on-new-same-origin-realm.js" so that the on-new-same-origin-realm.js script will execute before any other JavaScript code executes in the top realm execution environment, as well as any other child realm that matches its origin.

• Explainer¹ (minimally containing user needs and example code): https://github.com/WICG/Realms-Initialization-Control
• Security and Privacy self-review²: https://github.com/WICG/Realms-Initialization-Control#self-review-questionnaire-security-and-privacy
• GitHub repo: https://github.com/WICG/Realms-Initialization-Control
• Primary contacts (and their relationship to the specification):
  • Gal Weizman (Champion)
  • Yoav Weiss (Spec Mentor)
• Organization/project driving the design: ConsenSys
• External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5080729822953472

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• The group where the incubation/design work on this is being done (or is intended to be done in the future): WICG
• Existing major pieces of multi-implementer review or discussion of this design: None atm
• Major unresolved issues with or opposition to this design: None atm
• This work is being funded by: ConsenSys

[jyasskin]

Are you planning to, or have you talked to WebAppSec and TC39 about this feature?

[weizman]

Sure did, the community was rather interested in solving this issue as well as in the manner suggested:

• https://www.w3.org/2023/03/secure-the-web-forward/talks/realms.html
• https://www.w3.org/2023/03/secure-the-web-forward/report.html

(edit: as well as accepted to the WICG of course)

[weizman]

Is there any other information I can provide to assist you @jyasskin?

[jyasskin]

Sorry for dropping this. Secure the Web Forward isn't either of WebAppSec or TC39. Do you need introductions into those communities? I'm inclined to think that this is reasonable, but those communities have the deep expertise to notice risks or smoother ways to do this.