Re: [w3c/browser-payment-api] Specify UA requirements if “value” field of PaymentCurrencyAmount does not match syntax requirements (#260)

Right now the spec doesn't define any behaviour for this situation so I don't believe it is true that Chrome is not conforming. I think currently implementations can do what they want.

I'm not proposing that this is what the spec _should_ say, only what is or isn't said now. PR #256 is your proposal here. As I commented there, I was planning on a different solution to enable consistency between constructor and updateWith. That said, if the consensus is to throw in the constructor but do something else with updates then I could live with that. It just isn't my preference.

-- 
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/issues/260#issuecomment-247689355