Re: [w3c/manifest] Add id member to manifest (#988)

@dmurph commented on this pull request.



> +        application. When the user agent sees a manifest with an |identity|
+        matching that of an already-installed application, it SHOULD be used as
+        a signal that this manifest is a replacement for the already-installed
+        application's manifest, and not a distinct application, even if it is
+        served from a different URL than the one seen previously.
+        </p>
+        <p>
+          The |identity| MAY be used by a service that collects lists of web
+          applications to uniquely identify applications.
+        </p>
+        <p>
+          To <dfn>process the `id` member</dfn>, given [=object=]
+          |json:JSON|, [=ordered map=] |manifest:ordered map|:
+        </p>
+        <ol class="algorithm">
+          <li>Set |manifest|["id"] to |manifest|["start_url"].

If we allow start_url to always default to document url, then it could lead to confusion if a developer attaches a manifest on multiple pages (and they don't specify start_url), as, with the `id` member, this could mean each page could trigger an web app update to make that page now the new start_url of the app.

I guess my vote would be to make the behavior more predictable / less potentially weird  by requiring the start_url to be defined for the id to be considered? WDYT @philloooo?

-- 
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/pull/988#discussion_r685335490