Re: [w3ctag/design-reviews] Payment Handler (#231)

@dbaron: Excellent point! The specification makes the usage of instrument icons optional. From what I understand, Firefox plans to display each instrument individually together with their icons. Note that these icons might be different from what's in the web app manifest. A web app manifest for MyBank.com would have a bank logo, but the instrument icon for "Visa*1234" would be a VISA logo.

Chrome, on the other hand, plans to display a payment handlers as whole, without breaking it up into instruments. As such, Chrome will use name and icon from the web app manifest of the page that registers the payment handler. The web app manifest icons are downloaded and stored at the time of the payment handler registration. See https://rsolomakhin.github.io/pr/apps/ for demonstrations of web app manifest usage in Chrome. (The feature is enabled by default in Canary.) There're a few demos with missing web app manifests or missing icon information. If you open up the dev tools console, you will see warnings about the missing iconography in those cases.

Note that Chrome still uses the `capabilities` and `supportedMethods` fields of instruments to match payment handlers to PaymentRequest calls, so instruments are still useful to us.

-- 
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/231#issuecomment-366344619