Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768)

romandev commented on this pull request.

Yep, I'm implementing `retry()` feature in Chromium under @rsolomakhin's high-quality review.

>                        member is present, the user agent SHOULD display an error
                       specifically for each erroneous field of the shipping
                       address. This is done by matching each present member of
                       the <a>AddressErrors</a> to a corresponding input field
                       in the shown user interface.
                     </p>
+                    <p data-link-for="PaymentDetailsUpdate">
+                      Similarly, if <var>details</var>["<a>payerErrors</a>"]
+                      member is present and
+                      <var>request</var>.<a>[[\options]]</a>'s <a data-lt=
+                      "PaymentOptions.requestShipping">requestPayerName</a>,

nit: `<a data-lt="PaymentOptions.requestPayerName">`

>                        member is present, the user agent SHOULD display an error
                       specifically for each erroneous field of the shipping
                       address. This is done by matching each present member of
                       the <a>AddressErrors</a> to a corresponding input field
                       in the shown user interface.
                     </p>
+                    <p data-link-for="PaymentDetailsUpdate">
+                      Similarly, if <var>details</var>["<a>payerErrors</a>"]
+                      member is present and
+                      <var>request</var>.<a>[[\options]]</a>'s <a data-lt=
+                      "PaymentOptions.requestShipping">requestPayerName</a>,
+                      <a data-lt=
+                      "PaymentOptions.requestShipping">requestPayerEmail</a>,

nit: `<a data-lt="PaymentOptions.requestPayerEmail">`

>                        member is present, the user agent SHOULD display an error
                       specifically for each erroneous field of the shipping
                       address. This is done by matching each present member of
                       the <a>AddressErrors</a> to a corresponding input field
                       in the shown user interface.
                     </p>
+                    <p data-link-for="PaymentDetailsUpdate">
+                      Similarly, if <var>details</var>["<a>payerErrors</a>"]
+                      member is present and
+                      <var>request</var>.<a>[[\options]]</a>'s <a data-lt=
+                      "PaymentOptions.requestShipping">requestPayerName</a>,
+                      <a data-lt=
+                      "PaymentOptions.requestShipping">requestPayerEmail</a>,
+                      or <a data-lt=
+                      "PaymentOptions.requestShipping">requestPayerPhone</a> is

nit: `<a data-lt="PaymentOptions.requestPayerPhone">`

-- 
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/payment-request/pull/768#pullrequestreview-150089999