@jakearchibald > Of course not 😄. I said "The page" not "The browser". :smile: I seem to have misread you. > https://w3c.github.io/browser-payment-api/#show-method already rejects with a particular error if no supported payment apps are available. A site could use this as a trigger to display a list of recommendations. Yeah, this would probably work even without any further changes. One approach that might be sufficient, at least for version 1 of the specification, could be to figure out the best way for a merchant to use the existing behavior of the payment request api to implement recommendations on his web page, and then produce some really good examples that shows the best practices. I don't think there's a fingerprinting issue with the `show` method, since it potentially shows UI. I'd imagine one would prefer fingerprinting methods that weren't visible to the user. The `canMakePayment` method is a better candidate for fingerprinting. -- 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/48#issuecomment-276486478
Received on Tuesday, 31 January 2017 20:46:14 UTC