Scope Extensions Test
This test compares URLs inside and outside the scope granted by an
authorized web-app-origin-association file with an origin that
does not authorize this app.
Waiting for service worker to activate…
Instructions
Prerequisite: Configure the browser to accept WPT's
loopback certificate for https://127.0.0.1; otherwise, the
browser cannot retrieve the origin association. Chromium manual runs
should use WPT's SPKI allowlist through
--ignore-certificate-errors-spki-list rather than disabling
certificate verification globally.
-
Install this site as an app, then launch the installed app. Complete
the remaining steps from its app window.
-
Open the
authorized target.
It should remain in the app context and should not receive the user
agent's normal out-of-scope treatment.
-
Return to this page using Back. If the target opened in a separate tab
or window, close it instead.
-
Open the
target outside the association scope.
Its origin authorizes this app, but the URL is outside the path granted
by the association file, so it should receive the user agent's normal
out-of-scope treatment.
-
Return to this page using Back. If the target opened in a separate tab
or window, close it instead.
-
Open the
unauthorized target.
It should be treated as outside the app's scope, for example by opening
in a browser tab or by showing the user agent's normal out-of-scope UI.
-
The test passes if the authorized target inside the association scope
is treated as extended scope, while both other targets are treated as
out of scope.