Re: [w3c/manifest] Integration with service workers (#161)

@adrianhopebailie

> I'm not sure how to answer that question. Are you asking if I think it should be the same

Yes, that. If we're merging two things I want to make sure they're worth merging, or if you just want the processing model of the manifest, but it'd be a separate manifest.

> You're ignoring (in your example) the fact that neither ServiceWorker nor app manifest are limited to 1 per origin.

I'm not, it's at the heart of what I'm asking. Are developers likely to end up with a manifest for their site, and a separate manifest for their payment app?

> A mistake, in both cases, in my opinion.

Unfortunately that's not how the web's built today. Take github pages for example - one origin, many sites.

> If I visit foopay.com and I am prompted to install something,

So adding a payment app will require a permission prompt? Or will it require adding to home screen? I can't find reference to either :(

UAs are welcome to merge permissions to avoid confusion. Chrome has done this with push messages and notifications.

I'm trying to get to the root of why using manifest is so desirable here. Is it the reuse of a single resource? Is it the reuse of some processing models? Is it linked to some as-yet-undefined permissioning flow?

-- 
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/161#issuecomment-246341146