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

> I think the consensus was that for Web developers writing Javascript code and not needing to catch a raw request and inspect it to decide if it's a payment request felt more natural

If that's the reason, then `onmessage` isn't the answer, as the developer's still having to catch something raw. A specific payment event means you can have your own event object, with methods like `paymentEvent.plsShowThisUI(url)`.

I haven't looked at it enough to know if fetch or a custom event is better, but `onmessage` feels like a poor compromise.

-- 
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-243092932