Re: [w3c/manifest] Clarify behaviour of a page linking to a manifest that is not within scope of that manifest (#784)

I think that suggestion is really a separate feature to what's being proposed here. It's what I was referring to above with:

> This is an interesting use case ... which we should explore in the future, but through a dedicated API for installing a specific manifest, and likely with an associated permission.

Giving a site a means to explicitly trigger an install through a button (or link). What we're proposing here is that the normal semi-automated install mechanisms (showing an "install" button in the browser UI, automatically triggering the install prompt when enough engagement is reached, etc) would be allowed for a manifest that's out of scope.

-- 
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/784#issuecomment-533436621