Repository navigation
COOP: restrict-properties early review #760
Description
Wotcher TAG!
I'm requesting a TAG review of a new value for Cross-Origin-Opener-Policy: "restrict-properties".
This is the second iteration of trying to have crossOriginIsolated while interacting with cross-origin popups. The goal is still the same: be able to benefit from powerful APIs like SharedArrayBuffer without breaking interaction with cross-origin popups like Auth flows or payments.
- Explainer¹ (minimally containing user needs and example code): [url]
- Security and Privacy self-review²: [url]
- Primary contacts (and their relationship to the specification):
- [Arthur Hemery] ([github username]), [Google]
- [Camille Lamy] ([github username]), [Google]
- Organization/project driving the design: [Google]
- External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5072630953017344
Further details:
- [ X] 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): WHATWG
- The group where standardization of this work is intended to be done ("unknown" if not known): WHATWG
- Existing major pieces of multi-stakeholder review or discussion of this design: Allowing top-level communication for cross-origin isolated documents whatwg/html#6364
- Major unresolved issues with or opposition to this design: We'll be running an origin trial on Chrome to verify that there are no deployment blockers for web developers. The spec agreement should follow once we've demonstrated (or not) that this solution works.
- This work is being funded by: Google
You should also know that...
[please tell us anything you think is relevant to this review]
We'd prefer the TAG provide feedback as :
💬 leave review feedback as a comment in this issue and @-notify [hemeryar]
Activity
torgo commentedon Oct 18, 2022
Hi @hemeryar first our apologies for taking so long to get you feedback on this review. After reviewing it this week and going back to review our work on #649 it's not clear from the material you've provided how you've addressed the issues & questions we raised in that review. Can you provide a little primer here on the changes? Thanks - we will endeavour to get you a response more quickly.
58 remaining items
camillelamy commentedon Feb 8, 2024
Hi @torgo,
I have picked the worked up from @hemeryar. We've since moved the proposal to the WICG. Here is a link to the WICG explainer. That said, following the Origin Trial that Chrome ran, we are rethinking our approach with regards to making crossOriginIsolation more deployable. In particular, there are still issues with deployability not solved by COOP: restrict-properties (3rd party frames and COEP). We're looking at whether we can solve those and the issue of COI with popups at the same time. This means that we are likely to modify our proposal of COOP: restrict-properties from what is currently written in the explainer.
torgo commentedon Mar 18, 2024
@camillelamy thanks for that note. Has there been any progress or anything you'd like TAG feedback on?
torgo commentedon Apr 22, 2024
Hi @camillelamy has there been any update on this? It looks like the explainer may have moved? Can you update? Thanks!
camillelamy commentedon Sep 18, 2024
Hi @torgo, we have submitted a new API for TAG review that is meant to replace this proposal (new proposal: Document-Isolation-Policy). Do you still want me to update the explainer?
jyasskin commentedon Sep 18, 2024
Since you're no longer pursuing this issue's proposal, could you update https://github.com/WICG/coop-restrict-properties to say that and archive its repository? I'll close this issue.