Re: [w3ctag/design-reviews] Proliferation of manifests at W3C (#423)

@lknik said:

> Web Payment is another manifest.json, but the file location is indicated via HTTP header (not in a tag).

This is not entirely true. The browser finds out about the manifest first and foremost when a website calls Payment Request API and provides one or more payment methods it supports identified by their Payment Method Identifier (a URL).

Historically the browser used a `HEAD` to that URL to discover the manifest (URL of which was passed in a `Location` header) but the spec has been updated to support simply performing a `GET` to that URL which MAY return the actual manifest content. See https://github.com/w3c/payment-method-manifest/pull/37

i.e. There is no convention for the payment method manifest file name

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/423#issuecomment-542269021