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

dmurph left a comment (w3c/manifest#784)

@christianliebel said:
> 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.

I think I agree with this. I would want the install UX to effectively communicate what is happening.


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

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