Conversation
| <li>Let <var>manifest</var> be the manifest value created during <a> | ||
| steps to determine installability of the document</a>. | ||
| </li> | ||
| <li>Perform an unspecified sequence of actions to attempt to register |
There was a problem hiding this comment.
| <li>Perform an unspecified sequence of actions to attempt to register | |
| <li>Perform an [=implementation-defined=] attempt to register |
| the web application in the user's operating system (e.g., create | ||
| shortcuts that launch the web application, register the application | ||
| in the system uninstall menu, etc.). If the installation fails (which |
There was a problem hiding this comment.
The installation part needs a rewrite... it's kinda clumsy and hand-wavy (industry terms)
| the web application in the user's operating system (e.g., create | |
| shortcuts that launch the web application, register the application | |
| in the system uninstall menu, etc.). If the installation fails (which | |
| the web application in the user's operating system (e.g., create | |
| a means that launch the web application and perform necessary means | |
| for system integration etc.). | |
| </p> | |
| <p> | |
| If the installation fails (which |
| in the system uninstall menu, etc.). If the installation fails (which | ||
| can be for any reason, for example, the OS denying permission to the | ||
| user agent to add an icon to the home screen of the device), abort | ||
| these steps. |
There was a problem hiding this comment.
The installation process with or without BIP should be integrated. Then if installation fails, it aborts the BIP's promise.
| </li> | ||
| <li>The installation process can occur through an <dfn>automated | ||
| install prompt</dfn>: that is, a UI that the user agent presents to | ||
| the user when, for instance, there are sufficient <a>installability |
There was a problem hiding this comment.
installability signals are not a thing in the spec.
| <p> | ||
| In any case, the user agent MUST NOT <a>present an install prompt</a> | ||
| if the document is not <a>installable</a>. | ||
| </p> |
There was a problem hiding this comment.
| <p> | |
| In any case, the user agent MUST NOT <a>present an install prompt</a> | |
| if the document is not <a>installable</a>. | |
| </p> |
|
I wonder if we should rewrite this from scratch :/ ... this is very outdated now, both in prose and infrastructure. I'm worried it's going to take us just as long to massage it into shape than just rewrite it from scratch, but do it in smaller parts. It can certainly serve as a basis on which we build the new PRs, but as is... it's a bit ... argh. |
2 participants
Closes #???
(Reminder that we need to remove BIP from manifest incubations when it's merged back.)
This change (choose at least one, delete ones that don't apply):
Implementation commitment (delete if not making normative changes):
If change is normative, and it adds or changes a member:
Commit message:
Bring back
beforeinstallpromptPerson merging, please make sure that commits are squashed with one of the following as a commit message prefix:
Preview | Diff