Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179)

>            <p>The <code>shippingOptions</code> field is only used if the <a><code>PaymentRequest</code></a> was
>            constructed with <a><code>PaymentOptions</code></a> <code>requestShipping</code>
>            set to <code>true</code>.</p>
> +          <p class="note">
> +            If the sequence contains only one item or if the sequence has an item with the <code>selected</code>
> +            field set to <code>true</code>, then authors SHOULD ensure that the <code>total</code> field includes

Doesn't this mean that developers will have to write different code paths for total calculation based on whether or not they have a default shipping option for the customer? Wouldn't it be easier if the browser just fired the "shippingoptionchange" event when the UI appears if the developer sets the selected field? The general question here is what would result in an easier implementation for the developer?

---
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/179/files/bb719e40371a15bd1b84e0534bc91d05ce40a283#r62068123