Re: [w3c/manifest] Control which parts of the URLs belong to the app and which parts are not (#996)

> It sounds like you want to standardise manifest controls for Chromium's install/popout UI. The current title sounds like it's asking for the scope field.

They are essentially the same issue. It depends on how to solve the problem.

- From the perspective of standard: there should be more explanations or notes for installation/launching related behaviors. At present, these behaviors are not clearly defined in the spec, and I think browser's implementation is immature.
- From the perspective of browser implementation: I think it is wrong to assume that all URLs under the manifest's scope can be used to launch the app. The original intention of manifest's scope is used to determine whether the user has navigated outside the app.
- From the perspective of developers: the manifest can provide a new item for developers to define which URLs can be used to launch the app, or an API to control these behaviors. I initially considered from this perspective.

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