Hi @adamroach, (For the moment I'll pursue the idea that we can improve this proposal but I remain open to other proposals.) Key points for discussion (based on your comment): * Clearly defining user agent matching behavior when canMakePayment() is disabled. * Disabled by default (that is: "opt in"). I think that "opt in" should be "global" rather than "per site". * Enabled via standard permissions mechanism * I could go either way with "SHOULD" or "MUST" support configuration, but if the default mode is "disabled" then without configuration the functionality is meaningless. Thanks again for the input to the discussion! Ian -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-handler/pull/170#issuecomment-318801051
Received on Saturday, 29 July 2017 03:37:37 UTC