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

The Web Payments WG believes it has a use case that is appropriate here.

We currently intend to use ServiceWorkers to provide the functionality we require for a Payment App (See this [proposal](https://github.com/w3c/webpayments-payment-apps-api/blob/gh-pages/proposals/jsapi.md) and the thread [here](https://github.com/w3c/webpayments-payment-apps-api/issues/33)).

In our case we'd like the ability to register/install the app with some meta-data (supported payment methods) that would make sense to be include in an app manifest.

Since we are using ServiceWorkers though the current thinking is to extend the `ServiceWorkerRegistration` interface and use this to register this app metadata during registration of the ServiceWorker (see this example: https://github.com/w3c/webpayments-payment-apps-api/issues/33#issuecomment-242895193). 

If it were possible to use manifest to register a ServiceWorker without executing any code then browsers could determine meta-data about a payment app without needing to execute the registration code of the ServiceWorker itself.

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