application, it SHOULD treat that manifest as a description of a
distinct application, even if it is served from the same URL as that
of another application. When the user agent sees a manifest where
- |manifest|["id"] [=url/equal|equals=] the [=identity=] 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.
+ |manifest|["id"] is [=url/equal=] with [=URL serializer/exclude
+ fragment|exclude fragment true=] to the [=identity=] 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.
The [=identity=] can be used by a service that collects lists of web
@@ -1293,6 +1294,13 @@
[=Process the `id` member=] passing |json|, |manifest| and
|document URL|.
+
+ If the [=document=]'s [=document|processed
+ manifest=] is not null, and [=document=]'s [=document|processed
+ manifest=]'s id is not
+ [=URL/equal=] with [=URL serializer/exclude fragment|exclude fragment true=] to |manifest|["id"],
+ return.
+
[=Process the `scope` member=] passing |json|, |manifest|, and
|manifest URL|.
@@ -1421,7 +1429,55 @@
Updating the manifest
-
+
+ As specified for [^link/rel/manifest^] link relation, the manifest
+ is fetched and processed on every page load. When the [=processing
+ a manifest=] is successful, user agents MAY apply updated manifest
+ to any current and future application contexts associated
+ with the application.
+
+
+ For the purpose of updating, the following member are
+ security-sensitive members, as they are presented during
+ installation and on launch surfaces:
+
+
+
[=manifest/short_name=],
+
+
[=manifest/icons=]
+
+
[=manifest/name=],
+
+
+
+ User agents SHOULD NOT automatically apply changes to
+ [=security-sensitive members=] without [=express permission=] from
+ the user.
+
+
+ Instead, user agents SHOULD present changes to [=security-sensitive
+ members=] with appropriate management options, so the user can make
+ an informed decision about updating the web application.
+
+
+ The user agent MAY automatically apply the changes if the update
+ does not contain changes to [=security-sensitive members=].
+