diff --git a/index.html b/index.html index f4020d7ed..4f7702362 100644 --- a/index.html +++ b/index.html @@ -530,9 +530,11 @@
When shortcut item shortcut having - manifest is invoked, run the following steps: + manifest is invoked, run the steps to + launch a web application with manifest and + shortcut.url.
-A common use case of a manifest is for a user agent to install a web application; whereby the user agent - provides the end-user with a means of instantiating a new top-level + provides the end-user with a means of instantiating a new top-level browsing context that has the manifest's members applied to it. A web application that is installed is known as a installed web application. That is, the manifest's members, or - their defaults, are in effect on the top-level browsing context. + their defaults, are in effect on the top-level browsing context. This distinguishes an installed web application from a traditional bookmark, as opening a web page from a traditional bookmark will not have the manifest's properties applied to it.
-+
For example, on user agents that support installation, a web application could be presented and launched in a way that, to the end-user, is indistinguishable from native applications: such as appearing as a labeled icon on the home screen, launcher, or start - menu. When launched, the manifest is applied by the user agent - to the top-level browsing context prior to the start URL - being loaded. This gives the user agent an opportunity to apply the - relevant values of the manifest, possibly changing the display - mode and screen orientation of the web application. Alternatively, - and again as an example, the user agent could install the web - application into a list of bookmarks within the user agent itself. -
+ menu. When launching a web application, the manifest is + applied by the user agent to the top-level browsing + context prior to the start URL being loaded. This gives the + user agent an opportunity to apply the relevant values of the manifest, + possibly changing the display mode and screen orientation of the + web application. Alternatively, and again as an example, the user agent + could install the web application into a list of bookmarks within + the user agent itself. ++ At the discretion of the operating system or user agent, run the steps + to launch a web application with a + processed manifest. +
++ This would typically take place when the user selects an installed + web app from an app launching UI surface e.g., a home screen, launcher + or start menu. +
+ The steps to + launch a web + application is given by the following algorithm. The algorithm + takes a processed manifest manifest, + an optional URL target URL, an optional POST resource + POST resource and returns an application context. +
++ target URL, if given, MUST be within scope of + manifest. +
++ Other specifications MAY replace this algorithm's steps with their own + steps. This replacement will take effect for all invocations of + launch a web application. +
++ This algorithm is replaceable to allow an experimental + launch_handler + manifest field to configure the behavior of all web application + launches. The replacement algorithm invokes create a new application context by default but under certain conditions behaves + differently. +
+ The steps to create a new application context + is given by the following algorithm. The algorithm takes a + processed manifest manifest, + an optional URL target URL, an optional POST resource + POST resource and returns an application context. +
+It is RECOMMENDED that UI that affords the end user the ability to - install a web application also allows inspecting the icon, - name, start URL, origin, etc. pertaining to a web application. + install a web application also allows inspecting the icon, + name, start URL, origin, etc. pertaining to a web application. This is to give an end-user an opportunity to make a conscious decision to approve, and possibly modify, the information pertaining to the web application before installing it. This also gives the @@ -3163,13 +3223,13 @@
User agents SHOULD provide a mechanism for the user to remove an @@ -3189,11 +3249,11 @@
The navigation scope of a manifest is the "scope" item - of a processed manifest. The navigation scope restricts - the set of URLs to which an application context can be - navigated while the manifest is applied. + of a processed manifest. The navigation scope restricts + the set of URLs to which an application context can be + navigated while the manifest is applied.
-
- A URL target is said to be within scope of URL scope if the
+ A URL target is said to be within scope of URL scope if the
following algorithm returns true
:
- A URL target is within scope of a
+ A URL target is within scope of a
manifest if the target is within scope
of manifest's navigation scope (i.e., within scope of manifest's scope
member).