167417 2017-01-25 06:13:29 -0800 Implement <iframe allow="payment"> 2021-09-01 06:57:23 -0700 1 1 1 Unclassified WebKit DOM Safari Technology Preview Unspecified Unspecified RESOLVED DUPLICATE 229406 https://bugs.webkit.org/show_bug.cgi?id=226345 InRadar P2 Normal --- 1 zcorpan webkit-unassigned andersca brad.girardeau cdumez eric.carlson gsnedders hi jonlee marcos webkit-bug-importer oldest_to_newest 1269798 0 zcorpan 2017-01-25 06:13:29 -0800 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: https://github.com/whatwg/html/pull/2195 https://github.com/whatwg/html/pull/2217 Relevant w3c/web-platform-tests PRs: https://github.com/w3c/web-platform-tests/pull/4369 https://github.com/w3c/web-platform-tests/pull/4615 I will write more tests for same origin-domain; see https://github.com/w3c/web-platform-tests/issues/4526 1269865 1 jonlee 2017-01-25 10:04:39 -0800 Can we split this into 2 separate bugs? 1269945 2 zcorpan 2017-01-25 13:50:24 -0800 Done. This one is allowpaymentrequest; allowusermedia is bug 167430. 1764673 3 hi 2021-05-27 22:14:26 -0700 *** Bug 226345 has been marked as a duplicate of this bug. *** 1764674 4 hi 2021-05-27 22:14:53 -0700 <rdar://problem/33278860> 1789310 5 gsnedders 2021-09-01 06:57:23 -0700 forward duping to where things have actually been happening :( *** This bug has been marked as a duplicate of bug 229406 ***