← back to v150 · pwa-origin-migration
conformance · v150
v150 · pwa-origin-migration — conformance probe
6 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.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
destination-manifest-id-required |
The destination manifest declares a stable id before naming any predecessor app. spec ↗ | script | … | |
migrate-from-names-old-app-id |
The destination manifest's migrate_from entry names the installed app id from the old origin. spec ↗ | script | … | |
allow-migration-authorizes-destination-id |
The old origin's web-app-origin-association object authorizes the destination app id with allow_migration: true. spec ↗ | script | … | |
migration-behavior-values |
The migration behavior is either suggest or force, with suggest used for a passive rollout. spec ↗ | script | … | |
old-manifest-migrate-to-hint |
The old manifest can proactively point to the destination app id with migrate_to. spec ↗ | script | … | |
same-site-limitation |
The migration stays within the same site boundary rather than moving between unrelated registrable domains. spec ↗ | script | … |