Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507)

Looking at the spec some more, I may have been looking at the wrong part, maybe I should have been looking at:

https://www.w3.org/TR/payment-request/#dfn-shipping-address-changed-algorithm

> 17.1 Shipping address changed algorithm
>
> The shipping address changed algorithm runs when the user provides a new shipping address. It must run the following steps:
> 
> 1. Let request be the PaymentRequest object that the user is interacting with.
> 2. Let name be "shippingaddresschange".
> 3. Queue a task on the user interaction task source to run the following steps:
> > 1. Set the shippingAddress attribute on request to the shipping address provided by the user.
> > 2. Run the PaymentRequest updated algorithm with request and name.

It doesn't have any information on what to do in terms of not-having a listener for the shippingaddresschange event.

Again, I'm not very versed in reading specs, so it could be that the language is actually defining the behavior discussed in this issue and I'm not seeing it.

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