Re: [w3c/manifest] Add a unique identifier for a PWA (#586)

> @wanderview wrote:

>> The plan of record in service-worker-land is to default to scope when using the legacy single scope attribute and there is no id. If you are using the new-fangled-scope attribute that supports multiple scope values, etc, then you are required to set an explicit id.

> That's interesting, and eases my concern about multiple scopes inside a manifest. Is there a draft that we can read anywhere? Aligning manifest with Service Worker in this respect seems attractive.

I just want to highlight that in service-worker-land there is nothing like start_url, etc, to use as an id.  So falling back to scope as the default id is mainly because scope is the identifier today (since there is nothing else unique to use).  Since the fallback is for compatibility, it probably makes sense to fallback to whatever is currently being used as the id.  In this case it sounds like at least two browsers use start_url for that (if I have followed correctly).

-- 
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/586#issuecomment-781655797