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

Thank you for your reply, but my purpose is not to solve a personal problem.

> It should be noted that the install and launch icons mentioned here are behaviours of Chromium and aren't part of any spec.

Currently, on desktop OS, only Chromium-based browsers support to install a PWA. From developers' perspective, we care about the process of install and launch the app, and how to control it. When I transformed a web app to an installable PWA, I was thinking about:

- Do I need to add manifest link(`<link rel="manifest" href="/manifest.json">`) to all html files? Or only files that need to show the install icon.
- Do I need to add `serviceWorker.register('/sw.js')` code to all html files? Technically speaking, No. But adding it to all pages is usually not a problem.
- How to determine manifest's scope? consistent with service worker's scope? Does it affect installation prompts?Considering browser's launch icon, ideally, only the entry points of the app should be in the scope. Because the scope is a single string, not an array of string and don't support wildcard character. That affects the structure of directories and file names.

As you said, the spec does not define these, so I think this part needs to be considered in the specification, especially from the developer's point of view.

-- 
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-902504138