- From: Christian Liebel <notifications@github.com>
- Date: Mon, 19 Jan 2026 06:16:14 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1164/3768553361@github.com>
christianliebel left a comment (w3ctag/design-reviews#1164) @mkruisselbrink Thank you for your proposal. The TAG acknowledges that migrating a web app from one origin to another is a problem worth solving, and we support same-site migrations. We believe that the proposal, in its current form, is based on assumptions and specifications that don’t seem to have cross-vendor consensus. For example, web apps can also be installed without a manifest and, thus, without an ID. Acknowledging the "ID footgun," we ask you to discuss this restriction (which would _only_ apply to migrations) with the other vendors in the Web Apps WG. The URL used for the handshake reuses the location from Scope Extensions, which also does not have cross-vendor support. Regarding permissions, we recommend *not* migrating any existing permissions. Denying a permission as part of the migration after it was previously granted by a user seems problematic for user experience. Also, we are unsure if developers should be able to choose between the `"force"` and `"suggest"` update modes. Would developers not want to `"force"` an update in the default case? However, in that case, they would only be allowed to change the URL during the migration, and might not be able to perform the branding update in the same step. We would like you to consider an HTTP redirect as an alternative. This approach is not bound to manifests, and might be a little more versatile. For example, this could be limited to 301 Moved Permanently (i.e., `"force"` update mode), require appropriate headers to be set in the request and/or response (similar to CORS), or a redirect with a certain JSON payload that might give instructions on how to migrate permissions and data. We would like to hear your thoughts. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1164#issuecomment-3768553361 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1164/3768553361@github.com>
Received on Monday, 19 January 2026 14:16:18 UTC