(Finally getting back to PaymentRequest issues...) The spec as-written seems to be OK, with Chrome's implementation at fault. In particular the spec says that if the user adds or changes an address, a "shippingaddress" change event must be fired. It never says that the UI should be blocked until someone calls event.updateWith(). It sounds like some browsers may block the UI while this event is being fired, but that's not required by the spec in any way, as far as I can tell. As such I'm inclined to close this (perhaps filing a bug on Chrome about its UX). -- 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/507#issuecomment-296834708
Received on Monday, 24 April 2017 22:03:07 UTC