v148 · PWA · Web APIs
Data Preservation Sim
See which PWA data types survive the Chrome 148 manifest migration handshake automatically, which require manual service worker or app-level handoff, and which need a reset plan. Change the scenario, run the migration, and inspect each per-item verdict.
Migration scenario
18 MB exported from old origin
Include opaque cached responses
User clears old-origin data first
Old origin
https://app.example.com
→
New origin
https://www.example.com
Ready to simulate.
Auto-migrated by Chrome
Requires manual SW handoff
Cannot be migrated
Not yet processed
manifest migration declaration
// Old origin: app.example.com/manifest.json
{
"name": "My App",
"id": "/",
"migrate_to": {
"id": "https://www.example.com/",
"install_url": "https://www.example.com/install"
}
}
// New origin: www.example.com/manifest.json
{
"name": "My App",
"id": "/",
"migrate_from": [
{
"id": "https://app.example.com/",
"install_url": "https://app.example.com/install",
"behavior": "suggest"
}
]
}
// Old origin: /.well-known/web-app-origin-association
{
"https://www.example.com/": {
"allow_migration": true
}
}