Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)

I don't have a lot of time to reply in detail right now, but I chatted with @dominickng and will try to chat to @slightlyoff next week.

Dom and I have a rough consensus that we can make the requirements more predictable, and spec them. That should resolve the ongoing complaint that it's hard for developers to know when they'll be able to call this API (and differs across browsers and across time).

I think the specific *shape* of the API (`beforeinstallprompt` vs more ergonomic `install` method) is orthogonal to the changes being proposed. We can achieve all of the above rules without changing the API (though, perhaps it is good to have a clean break and change the API surface at the same time).

A request: can we stop using `alert` as an analogy for install prompts? Alert is widely regarded as a mistake, and we should not be using its existence as an excuse for designing similar APIs. I find a more helpful analogy is just the fact that sites can show their own internal HTML prompt or scrim on top of their own content. To me, that justifies an API that shows a prompt over the developer's own content.

-- 
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/627#issuecomment-381857708