Bug 167417 - Implement <iframe allow="payment">
Summary: Implement <iframe allow="payment">
Status: RESOLVED DUPLICATE of bug 229406
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Keywords: InRadar
Depends on:
Reported: 2017-01-25 06:13 PST by Simon Pieters (:zcorpan)
Modified: 2021-09-01 06:57 PDT (History)
9 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Simon Pieters (:zcorpan) 2017-01-25 06:13:29 PST
I guess WebKit doesn't implement PaymentRequest or getUserMedia() yet(?), but filing this anyway...

<iframe allowpaymentrequest> controls if an iframe can access the PaymentRequest API.

<iframe allowusermedia> controls if an iframe can access the getUserMedia() API.

On the spec side:

* When a document is initialized (https://html.spec.whatwg.org/#creating-a-new-browsing-context and https://html.spec.whatwg.org/#initialise-the-document-object ), https://html.spec.whatwg.org/#set-the-allow*-flags is run, which can set "allowpaymentrequest flag" and "allowusemedia flag" on Document.
* PaymentRequest constructor calls https://html.spec.whatwg.org/#allowed-to-use : https://github.com/w3c/browser-payment-api/pull/383
* getUserMedia also call allowed to use: https://github.com/w3c/mediacapture-main/pull/427

Relevant whatwg/html PRs:


Relevant w3c/web-platform-tests PRs:


I will write more tests for same origin-domain; see https://github.com/w3c/web-platform-tests/issues/4526
Comment 1 Jon Lee 2017-01-25 10:04:39 PST
Can we split this into 2 separate bugs?
Comment 2 Simon Pieters (:zcorpan) 2017-01-25 13:50:24 PST
Done. This one is allowpaymentrequest; allowusermedia is bug 167430.
Comment 3 Devin Rousso 2021-05-27 22:14:26 PDT
*** Bug 226345 has been marked as a duplicate of this bug. ***
Comment 4 Devin Rousso 2021-05-27 22:14:53 PDT
Comment 5 Sam Sneddon [:gsnedders] 2021-09-01 06:57:23 PDT
forward duping to where things have actually been happening :(

*** This bug has been marked as a duplicate of bug 229406 ***