Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404)

marcoscaceres approved this pull request.

LGTM, bar nit. 

>                <dfn>[[\details]]</dfn>
             </td>
             <td>
               The current <a>PaymentDetails</a> for the payment request
               initially supplied to the constructor and then updated with calls
               to <a data-lt=
-              "PaymentRequestUpdateEvent.updateWith">updateWith()</a>.
+              "PaymentRequestUpdateEvent.updateWith">updateWith()</a>. Note
+              that all <a data-lt="PaymentDetailsModifier.data">data</a>
+              members of <a>PaymentDetailsModifier</a> instances contained in
+              the <a data-lt="PaymentDetails.modifiers">modifiers</a> member
+              will be removed, as they are instead stored in serialized form in
+              the [[\serializedModifierData]] internal slot.

nit: link to `<a>[[\serializedModifierData]]</a>`. I'll eventually teach ReSpec about internal slots :( 

-- 
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/404#pullrequestreview-17856869