- From: Ade Bateman <notifications@github.com>
- Date: Thu, 15 Sep 2016 21:59:06 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Friday, 16 September 2016 04:59:46 UTC
The problem with this change is that it doesn't deal with the updating case where throwing isn't a possibility. Just like in #249 it would have been easy to throw in the constructor in this situation but then the behaviour would be inconsistent in `updateWith()`. We didn't really want the bad update to cause the payment request to be terminated because doing so looks like a user agent bug and not a page bug. Also it will be easier to debug the problem when a user explains what happens. So for the currency value I'd prefer a different proposal. -- 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/256#issuecomment-247518532
Received on Friday, 16 September 2016 04:59:46 UTC