Intent to Prototype: Related Website Partition (RWP) API

91 views
Skip to first unread message

Dylan Cutler

unread,
Mar 24, 2025, 10:46:26 PMMar 24
to blin...@chromium.org, Johann Hofmann, Ari Chivukula

Explainer

https://github.com/explainers-by-googlers/related-website-partition-api

Specification

None

Summary

The Related Website Partition (RWP) API is a novel mechanism for providing third-party embeds access to a partitioned, non-cookie storage handle which allows them to continue a single session across multiple domains in the same Related Website Set.


Related Website Sets (RWS) introduces a new privacy boundary on the web which allows sites to have access to their unpartitioned cross-site state when they are embedded on other related sites.


Blink component

Blink > Storage  

Motivation

Some third-party SaaS developers embed their content on sites which are part of a Related Website Set and wish to maintain a continuous session across multiple sites within that set.


The RWP API provides a way for third parties to maintain a single session across sites in an RWS using storage that does not prompt the user and is limited only to activity within that set. This is in contrast to using the Storage Access API, which does prompt the user and grants the third party access to activity outside the current RWS.

 

Initial public proposal

https://github.com/WICG/first-party-sets/issues/94#issuecomment-2138292885

TAG review

https://github.com/w3ctag/design-reviews/issues/1047

TAG review status

Open but no feedback yet.

Risks Interoperability and Compatibility

None

Gecko: No signal

WebKit: No signal

Web developers: No signal

Other signals: N/A

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No

Debuggability

None

Is this feature fully tested by web-platform-tests?

No

Flag name on chrome://flags

TBD

Finch feature name

TBD, likely kRelatedWebsitePartitionAPI

Non-finch justification

None

Requires code in //chrome?

The implementation of the feature would not depend on code in //chrome.

We may modify the browser UI defined in //chrome which provides information about Related Website Sets.

Tracking bug

https://crbug.com/394354282

Estimated milestones

We will do an Origin Trial in M137 or M138

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5184475929247744


Reply all
Reply to author
Forward
0 new messages