Re: [w3c/manifest] Clarify circumstances in which BeforeInstallPromptEvent.prompt() may be called (#691)

> I had the mini-infobar in mind but if it's a component in the UA land ... obviously it wont be an issue and the opt-in does not make sense.

It could be either. From a spec standpoint, certainly the infobar versus an icon in the address bar are the same (they're both non-page content so they're outside the realm where the spec can dictate UA behaviour).

> I consider that the rendered content is not a part of the UA interface so if a UA component invade the content space, the spec should give the possibility to control it. That's why I was for the option 1, but as you said, it's all about UA responsibility.

The thing is that Chrome, at least, shows infobars "invading the content space" all the time, for many things which are not specced, and don't give developer control. For a few examples:

* Offering to translate a page if the browser detects a different language.
* Offering to turn on data saver if the page is using too much bandwidth.
* Offering to render the page better for mobile, if the page seems to not be designed for mobile.

The infobar to install the app is fairly in-line with other parts of the Chrome UI and I believe all browsers have similar features. Having said that, we recognise that it's a bit heavy-handed to show this all the time so we're looking at more subtle UI.

> Just a last thing, I still don't understand how option 1 (opt-in) can be compatible with option 2 & 3 (auto) in Proposal 2. Is that mean the opt-in feature wont be described as a part of the spec but UA can implement it if they want ?

Yeah, Proposal 2 just means that BeforeInstallPrompt is *only* used to control manual prompting, and isn't tied to automatic prompt at all. Thus:

* Cancelling the event does not suppress any automatic prompt that the browser may or may not show.
* The browser is not required to fire BeforeInstallPrompt before showing the prompt.

Automatic prompts are purely a UA-specific feature which the spec says nothing about, normatively (contrary to the spec today which explicitly talks about automatic prompts). A UA could choose to never show an automatic prompt (Option 1) or to show one, but not tied to the BeforeInstallPrompt event (Option 2 or 3).

-- 
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/691#issuecomment-409069318