← back to v147 · pwa-origin-migration

conformance · v147

v147 · pwa-origin-migration — conformance probe

7 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.

browser: spec: https://github.com/WICG/manifest-incubations/blob/gh-pages/pwa-migration-explainer.md chromestatus: #5123349239955456 generated 2026-06-05T10:20:39Z by codex-showcase-auto-research
0
pass
0
fail
0
blocked
7
total
id contract kind verdict detail
destination-manifest-declares-migrate-from The destination app manifest declares migrate_from and includes a stable id. spec ↗ script
old-origin-authorizes-destination The old origin web-app-origin-association file explicitly authorizes the destination app with allow_migration: true. spec ↗ script
one-sided-claim-is-not-enough A migrate_from claim without matching old-origin authorization is rejected by the validator. spec ↗ script
same-site-migration-only The same-site restriction allows subdomain-to-subdomain moves under example.com and rejects example.com to example.net. spec ↗ script
migrate-to-points-at-destination-install-url The optional old-app migrate_to object carries both the destination id and a valid install_url. spec ↗ script
behavior-flag-is-suggest-or-force The migrate_from behavior flag accepts suggest or force, and rejects unrelated values. spec ↗ script
redirected-old-app-needs-install-url When old routes redirect, the object form of migrate_from can provide a non-redirecting install_url for update checks. spec ↗ script