[blink-dev] Intent to Prototype: Partitioned Popins

212 views

Skip to first unread message

Ari Chivukula

unread,

May 20, 2024, 8:07:53 AMMay 20

to blink-dev, Johann Hofmann, Kaustubha Govind

Contact emails

ari...@chromium.org, joha...@chromium.org, kaust...@chromium.org

Explainer

https://github.com/arichiv/partitioned-popins/

Summary

A new web primitive is needed to cover short-lived popup use cases which require access to storage partitioned by the popup opener. This primitive should be private and secure by default, while providing a consistent UI experience across user agents.

To solve this need, we propose the “Partitioned Popin”, a type of pop-up for loading web content with two unique new features: a modal-like UI relative to its opener tab and cookies/storage being partitioned to its opener context.

Blink component

Blink>Storage

Motivation

Many smaller businesses and applications on the web currently use third-party vendors to perform or facilitate security sensitive operations such as authentication. These third-party vendors prefer to be loaded in top-level contexts so that they are not subject to clickjacking or script injection attacks by a compromised relying party.

This ‘popin’ could be useful for any sites wanting a consistent way to prompt the user to interact with a new window in a way that makes it clear what site initiated the interaction. Making the ‘popin’ partitioned by its opener ensures the privacy of an iframe (restricting access to first-party storage) while retaining the security of a top-level navigation (isolating the process).

TAG review

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

Compatibility

This adds a new feature without removing existing ones.