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

The spec currently states no UA requirements that can be implemented or tested for the `value` field of `PaymentCurrencyAmount` objects; [it uses RFC 2119 MUSTs to specify syntax requirements for the `value` field](https://w3c.github.io/browser-payment-api/#dfn-value), but doesn’t actually state what UAs must do for a `value` that does not match the syntax requirements.

So at this point the only relevant test case I can write for `value` is to check that the UA doesn’t throw if the `value` doesn’t match the syntax requirements—because the spec does not say the UA must throw. (And currently Chrome does actually throws for such a `value`, so [Chrome is not conforming to the current spec here](https://bugs.chromium.org/p/chromium/issues/detail?id=647766)).

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