Re: [w3c/manifest] Bring back "serviceworker" member (#864)

The "serviceworker" field is used for just-in-time installation. For a demo, see https://rsolomakhin.github.io/pr/skip-ui/, which will install a service worker from `https://bobpay.xyz`. This is almost equivalent to a merchant using `window.open("https://bobpay.xyz")` and then `https://bobpay.xyz` installing it's service worker on page load.

Background: https://www.w3.org/blog/wpwg/2018/08/20/further-streamlining-the-payment-request-user-experience/#jit

Original decision to not spec just-in-time install: https://github.com/w3c/payment-handler/issues/240

New discussions to spec it: https://github.com/w3c/payment-handler/issues/346

Moving `"serviceworker"` field to https://w3c.github.io/payment-method-manifest/ does not sound exactly right to my ear, because Web Payments also uses multiple fields in web-app manifest, some of which are not used anywhere else. For example:

* `"name"`
* `"icons"`
* `"prefer_related_applications"`
* `"related_applications.platform"`
* `"related_applications.id"`

Only used in Web Payment, as far as I know:

* `"related_applications.min_version"`
* `"related_applications.fingerprints.type"`
* `"related_applications.fingerprints.value"`

These fields appear to make more sense to me in the web-app manifest, but maybe I'm biased. What's the right thing to do?

-- 
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/864#issuecomment-625751553