- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 03 Apr 2017 01:10:32 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 April 2017 08:11:06 UTC
In the "Shipping address changed algorithm", the spec says: > Set the shippingAddress attribute on request to the shipping address provided by the user. However, it gives no guidance about null values incoming from the information source for the `ShippingAddress`. As such, a lot of those attributes could end up as empty strings. That's ok, but it's not clear in the spec what to do. It's also ambiguous in that "new PaymentAddress" is never actually called (even though it has no declared constructor). -- 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/495
Received on Monday, 3 April 2017 08:11:06 UTC