- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 16 Jan 2019 00:36:26 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/payment-request/pull/822/review/193020336@github.com>
annevk commented on this pull request. > </h2> - <p data-tests= - "allowpaymentrequest/active-document-cross-origin.https.sub.html, allowpaymentrequest/active-document-same-origin.https.html, allowpaymentrequest/allowpaymentrequest-attribute-cross-origin-bc-containers.https.html, allowpaymentrequest/allowpaymentrequest-attribute-same-origin-bc-containers.https.html, allowpaymentrequest/basic.https.html, allowpaymentrequest/no-attribute-cross-origin-bc-containers.https.html, allowpaymentrequest/no-attribute-same-origin-bc-containers.https.html, allowpaymentrequest/removing-allowpaymentrequest.https.sub.html, allowpaymentrequest/setting-allowpaymentrequest-timing.https.sub.html, allowpaymentrequest/setting-allowpaymentrequest.https.sub.html"> - To indicate that a cross-origin <a>iframe</a> is allowed to invoke the - payment request API, the <a>allowpaymentrequest</a> attribute can be - specified on the <a>iframe</a> element. + <p> + The <a data-cite="feature-policy">Feature Policy</a> specification + defines the "<code>payment</code>" feature and the <code><dfn data-cit= You cannot get to REC without two implementations right? And implementations wouldn't be able to implement this any other way. Or would you leave this whole thing undefined or some such? -- 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/822#discussion_r248189727
Received on Wednesday, 16 January 2019 08:36:49 UTC