From 95340396bd9a7067298b126f24770155cd73ae81 Mon Sep 17 00:00:00 2001
From: Phillis Tang
+ The manifest is fetched and processed on every page load. When the
+ processing is successful, user agents MAY apply updated manifest to
+ any current and future application contexts
+ associated with the application.
+
+ When the user agent fetches a manifest as part of an update check,
+ it MUST [=url/equal|compare=] the fetched processed manifest's
+ [=manifest/identity=] with the identity of the app being updated. If
+ it is not equal, the user agent MUST NOT update the installed
+ application's manifest.
+
+ User agents SHOULD be careful about performing update to manifest
+ fields like app name and icons. Users should be fully aware if
+ such fields are to be be updated to avoid web applications being
+ installed and silently changed to appear as a different one.
+
Updating the manifest
+
+ Privacy and security consideration
+
+
such fields are to be be updated to avoid web applications being
installed and silently changed to appear as a different one.
+ User agents SHOULD be careful about performing update to manifest + fields like app name and icons. Users should be fully aware if + such fields are to be be updated to avoid web applications being + installed and silently changed to appear as a different one. +
When the user agent fetches a manifest as part of an update check, it MUST [=url/equal|compare=] the fetched processed manifest's @@ -1222,17 +1228,6 @@
- User agents SHOULD be careful about performing update to manifest - fields like app name and icons. Users should be fully aware if - such fields are to be be updated to avoid web applications being - installed and silently changed to appear as a different one. -
-
The manifest is fetched and processed on every page load. When the
processing is successful, user agents MAY apply updated manifest to
From ff204a058eb38c10818c630f571ddab5aae0b917 Mon Sep 17 00:00:00 2001
From: Phillis Tang
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 @@ -1282,6 +1283,13 @@
- The manifest is fetched and processed on every page load. When the - processing is successful, user agents MAY apply updated manifest to - any current and future application contexts + For installed web application, the manifest is fetched and processed + on every page load. When the processing is successful, user agents + MAY apply updated manifest to any current and future application + contexts associated with the application.
@@ -1422,13 +1431,6 @@
- When the user agent fetches a manifest as part of an update check, - it MUST [=url/equal|compare=] the fetched processed manifest's - [=manifest/identity=] with the identity of the app being updated. If - it is not equal, the user agent MUST NOT update the installed - application's manifest. -
From 4e64aa428e7e563a69f1a983d90f10cd03701de1 Mon Sep 17 00:00:00 2001 From: Yajing Tang- For installed web application, the manifest is fetched and processed - on every page load. When the processing is successful, user agents - MAY apply updated manifest to any current and future application - contexts - associated with the application. + 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.
User agents SHOULD be careful about performing update to manifest
From 4669fbf6e7f0e79398700cd5e3d0af7c1e076411 Mon Sep 17 00:00:00 2001
From: Yajing Tang
with the application.
- User agents SHOULD be careful about performing update to manifest - fields like app name and icons. Users should be fully aware if - such fields are to be be updated to avoid web applications being - installed and silently changed to appear as a different one. + For the purpose of updating, the following member are + security-sensitive members, as they are presented during + installation and on launch surfaces:
++ 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=]. +
+ From c67e4565994c1219d02b462ab5fa26aacd1662a5 Mon Sep 17 00:00:00 2001 From: Phillis Tang