Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33)

@jakearchibald, to address your other comment:

> Landing stuff in `onmessage` that wasn't sent via the user's call to `postMessage` feels weird.

That's true and is probably a good reason to not use an HTTP request and `onfetch` too.

The more I think about it it feels like if we're designing a new API in `navigator` scope then it makes sense for this to have a corresponding new API in `ServiceWorker` (and possibly `ServiceWorkerRegistration`) scope too.

I.e. If we aren't forcing websites to submit a payment request using `fetch` or `postMessage` then we shouldn't force a payment app to process them through `onfetch` or `onmessage`.

So, I'm coming around to @dlongley 's proposal. Still keen to hear what @adamroach thinks though.

-- 
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/webpayments-payment-apps-api/issues/33#issuecomment-243091977