Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)

I think this is dependent on what happens during installation:

On Chromium-based browsers on desktop and for the `standalone` display mode, the page linking to the manifest "leaves the tab" after installation. The tab is closed, and the current page is opened in a new window with the manifest applied. In this scenario, the current page can indeed be outside the scope.

However, this is not an issue on Safari, as the application is added to the dock/home screen but _not_ automatically launched with the current page. When the user opens the app, the `start_url` is loaded. When no `start_url` was defined, it falls back to the page linking to the manifest. The processed start URL is guaranteed to be in scope, as the scope will otherwise be adjusted to include the start URL.

Our spec does not define what should happen after installation, so I'm unsure if we should specify this at all. Installing apps from an out-of-scope page is currently possible, so changing this may break existing users, and it does not lead to problems in Safari. Chromium could solve this issue by not opening the current page in the window if it is out of scope, showing UI to redirect the user to the start URL of the app, etc.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/784#issuecomment-2473055457
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/784/2473055457@github.com>