Re: [w3c/browser-payment-api] The shippingOptions field is used in more cases than the spec claims, as far as I can tell (#345)

I think it's a bug in the updateWith text. Right now it says:

> If details contains a shippingOptions sequence, then:

Perhaps it should say:

> If requestShipping is true and if details contains a shippingOptions sequence, then:

But then the question seems to become: what happens if details.shippingOptions is provided but requestShipping is not true. It seems like ignoring is best, but I guess throwing is more explicit. @adrianba ?

-- 
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/345#issuecomment-266877997