Re: [w3c/browser-payment-api] Reference HTML for allowpaymentrequest definition (#359)

zcorpan commented on this pull request.



>        </p>
       <p>
-        The <a>HTMLIFrameElement</a> is extended with an
-        <dfn><code>allowpaymentrequest</code></dfn> content attribute.
-        <a>allowpaymentrequest</a> is a <a>boolean attribute</a>. When
-        specified, it indicates that scripts in the iframe element's browsing
-        context are <dfn>allowed to make payment requests</dfn> (if it's not
-        blocked for other reasons, e.g., there is another ancestor iframe
-        without this attribute set).
+        When an <a><code>iframe</code></a> element has an
+        <a><code>allowpaymentrequest</code></a> attribute, and does not
+        have any ancestor <a><code>iframe</code></a> element without an

This seems wrong. This reads like it's talking about ancestor the DOM concept. But you should hook into "allowed to use" instead, which handles nested browsing contexts. See Fullscreen.

-- 
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/359#pullrequestreview-11328697