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

> I'm not willing to merge a normative change of this magnitude without confirmation from the WG, sorry.

I'm completely supportive of this being a working group decision - but it's absolutely unfair for you to  assume that members of the WG understand the implications or even what WebIDL is (just scroll up to see what I mean!). This is not a political or consensus thing - if the data is not valid, then users could get charged the wrong amount or accidentally misled (see #541 - where if the `.data` is screwed up, then certain display items won't show up or the total won't match!). 

As this directly affects browser engines, it's on browser engine people to explain to the WG who don't know WebIDL what the implications are. Otherwise, it's impossible for the WG to make an informed decision on this - and at least, from a Firefox perspective, we will willfully violate the spec where it could negatively impact users (like in this case).


-- 
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-305677189