Third-party origin trials

Origin trials can now be enabled by embedded scripts, based on tokens matching their third-party origin. Previously, it was possible for scripts to enable origin trials, but only when the token matches the origin of the containing document.

Motivation

Allow third-party providers to experiment more effectively via origin trials. As in the origin trials explainer (see doc links), the goal is to encourage broad participation and feedback from web developers, while preventing burn-in of features or hampering iteration. Origin trials currently require opt-in/attribution for first-party origins, which causes undue friction for third-party providers. For some features, third-party providers are often in the best position to experiment and provide feedback.

Documentation

• https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/explainer.md
• https://docs.google.com/document/d/1xALH9W7rWmX0FpjudhDeS2TNTEOXuPn4Tlc9VmuPdHA/edit

Status in Chromium

Blink components: Internals>OriginTrials

In development (tracking bug)

Consensus & Standardization

• Firefox: No signal
• Edge: No signal
• Safari: No signal
• Web Developers: No signals

Owners

• chasej@chromium.org
• rodneyding@google.com
• experimentation-dev@chromium.org

Search tags

Last updated on 2020-10-25