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

> @@ -425,6 +425,13 @@
>              length of 1, then set <a><code>shippingOption</code></a> to the <code>id</code> of
>              the only <a><code>ShippingOption</code></a> in the sequence.
>            </li>
> +          <li>
> +            If <code>details</code> contains a <code>shippingOptions</code> sequence with a
> +            length greater than 1, and if any <a><code>ShippingOption</code></a> in the sequence
> +            has the <code>selected</code> field set to <code>true</code>, then set
> +            <a><code>shippingOption</code></a> to the <code>id</code> of the last <a><code>ShippingOption</code></a>
> +            in the sequence with <code>selected</code> set to <code>true</code>.
> +          </li>

Sure, that's fine. I just want such behavior to be technically conformant. The conformance section of this document denotes everything except a named list of items as normative, and this step -- which specifies that the shippingOption is set a certain way -- doesn't fall into any of the named non-normative categories. That makes performing such action mandatory for conformance purposes, and I think that's too strict.

---
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#r62103526