← Back to release summary

Web app scope extensions

Category
Miscellaneous
Type
New or changed feature
Status
In development (Chrome In development)
Intent stage
Start prototyping

Summary

Adds a "scope_extensions" web app manifest field that enables web apps to extend their scope to other origins. Example usage: { "name": "Example", "display": "standalone", "start_url": "/index.html", "scope_extensions": [ {"type" : "origin", "origin" : "https://example.com"} ] } This allows sites that control multiple subdomains and top level domains to be presented as a single web app. Requires listed origins to confirm association with the web app using a .well-known/web-app-origin-association configuration file. { "https://sample-app.com/": { "scope": "/" } }

Motivation

Web app scope (defined by the scope field) can only be defined with a path from a single origin. It is used to determine whether an app window's current document is a part of the app. It also determines what URLs are allowable in other manifest members. With "scope_extensions", developers are able to expand the behaviors of their app to include other origins if there is agreement between the primary origin of a web app and the associated origins.

Standards & signals

Docs: https://docs.google.com/document/d/1-idhx8heajbPYl3cdXFVCjpIuf96cRa_DrRk6147ELI/edit?usp=sharing

Samples: https://main-pwa-origin-2.glitch.me

Explainers: https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md

View on chromestatus.com