Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822)

ianbjacobs 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=
+        "feature-policy#attr-iframe-allowpaymentrequest">allowpaymentrequest</dfn></code>
+        attribute for <a>iframe</a> element, which control whether a particular
+        document, including cross-origin documents, is <a>allowed to use</a>
+        the <a>PaymentRequest</a> interface. Please refer to the <a data-cite=
+        "feature-policy">Feature Policy</a> specification for usage examples,
+        implementation details, and normative conformance requirements.

I think you can drop "normative" and just leave "conformance requirements."

-- 
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#pullrequestreview-192661318