Re: [w3c/browser-payment-api] Reject acceptedPromise if converting method data fails (#536)

I have reviewed the minutes of the 8 June call and don't wish to block what appears to be consensus from the editors on a path forward.

I am disappointed that the editors appear to have effectively ignored the input that @dlongley, myself and others have provided for over 2 years on the bigger issue in favor of getting a decision on what to them seems likely a very minor issue.

We now have a design that makes it very difficult for decentralized payments systems to define a payment method that can be used by the Payment Request API but very easy for the incumbent monopoly (EMVCo) to maintain the status quo.

I honestly think that the browser experts pushing this work forward don't appreciate or understand the impact or magnitude of what they are doing to an industry they know very little about, but when my comments are deleted to avoid further discussion then I think I have exhausted my options in trying to change that.

The Web platform is littered with design decisions that are looked back on with great regret, usually because they were made without due consideration of the side-effects, I hope this is not one of them.

-- 
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/browser-payment-api/pull/536#issuecomment-307813932

Received on Monday, 12 June 2017 14:54:24 UTC