I'd prefer to make it clear that `error` is used only for shipping option related errors and will be ignored if `requestShipping` is `false` or `shippingOptions` is non-empty. The error message is for the user selected shipping address, so `shippingAddressError` would be a better name. However, I'd prefer to avoid such disruptive rename. Can we keep the `error` name, but clearly annotate it in the spec instead? -- 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/451#issuecomment-285728607
Received on Friday, 10 March 2017 17:18:17 UTC