Re: [w3ctag/spec-reviews] IFrame support in web payments (#147)

At first glance, the spec seems a bit informal, i.e., lacking a clear processing model.  Such a model would make it clearer what happens in the case of nested iframes.  Is the <code>allowpaymentrequest</code> attribute needed on the iframe at each origin boundary between the browsing context that wants to be allowed to make payment requests and the toplevel browsing context, or is it needed on more or fewer iframes?

Also, why is this extending only <code>HTMLIFrameElement</code> and not also <code>HTMLFrameElement</code> and <code>HTMLObjectElement</code>?  Those are the three interfaces that have a <code>contentDocument</code> property.  That said, the [allegedly-deprecated](https://bugzilla.mozilla.org/show_bug.cgi?id=287465) ([the editor's draft](https://svgwg.org/svg2-draft/struct.html#InterfaceGetSVGDocument) sort of agrees) <code>getSVGDocument()</code> seems to be on 2 of the 3 (not <code>HTMLFrameElement</code>, but with <code>HTMLEmbedElement</code> added.  Maybe a common interface here is needed...

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/147#issuecomment-262400109