Re: [w3c/manifest] Control over webapp installation & launch (#705) from frlinw on 2019-07-25 (public-webapps-github@w3.org from July 2019)

From: frlinw <notifications@github.com>
Date: Thu, 25 Jul 2019 04:14:13 -0700
To: w3c/manifest <manifest@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/manifest/issues/705/515003620@github.com>

You can trigger the install button in userland
![image](https://user-images.githubusercontent.com/11896237/61868593-00246700-aeda-11e9-8e7a-4a5cd456cde7.png)
You can't trigger the (new in Chrome) "open with" button in userland
![image](https://user-images.githubusercontent.com/11896237/61868668-2ba75180-aeda-11e9-96a8-1ae520790faf.png)
these 2 actions are related and could be supported by the spec.

It's different from the service worker launch proposal linked by @dominickng. In the proposal, the launch event is designed `to prevent certain incoming navigations` so it's not controllable by the webauthor.
Note: Here I'm targeting future navigation and not 'after installation' action

I know there is already a UA adoption issue with beforeinstallprompt, what are the reasons to not implement it (for firefox at least)? Is it in a status quo state?

-- 
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/issues/705#issuecomment-515003620

Received on Thursday, 25 July 2019 11:14:35 UTC