Re: [browser-payment-api] Add a reference to issue #40. (#72)

> @@ -275,6 +275,15 @@
>            list, the payment <code>details</code>, the payment <code>options</code>, and any <a>payment
>            method</a> specific <code>data</code>.
>          </p>
> +
> +        <p class="issue" data-number="40" title="How do developers layer additional information in the core payment messages?">
> +          How does a developer access the <code>data</code> object?
> +          How is <code>data</code> sent to the payment app?
> +          Are the core set of payment messages (request/response) extensible?
> +          If they are extensible, what is the extensibility mechanism?
> +          Is the browser required to understand this extensibility mechanism?
> +        </p>
> +

Works for me, happy to go w/ the issue text the group agreed to. I trust that the editors will use the issue text you pointed to.

---
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/72/files/d68d537810248de89da6f156b51cea760aaab6cd#r56663972