From 77c3272f23750a3ccbfaf9684792aa851bd28299 Mon Sep 17 00:00:00 2001
From: Marcos Caceres
allowlist/'self'=], which means third-party contexts are not [=allowed
to use=] the API by default.
+ It is OPTIONAL for user agents for user agents to support + [[[PERMISSIONS-POLICY]]]'s `Permissions-Policy` HTTP header. +
Developers can use the means afforded by the [[[permissions-policy]]] specification to control if and when a third-party context is [=allowed @@ -708,6 +712,11 @@
+ The Working Group expects to make the `Permissions-Policy` HTTP + header mandatory in a future revisions of this specification, once + the header is more widely supported. +
- It is OPTIONAL for user agents for user agents to support + It is OPTIONAL for user agents to support [[[PERMISSIONS-POLICY]]]'s `Permissions-Policy` HTTP header.
From 89cf57daf0eafd63b6888b8c6330e6fa79f4dd5d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tantek=20=C3=87elik?=
Although user agents are unified in preventing the Web Share API from
being used in third-party context, at the time of publication there
- are interoperability with relying on the [[[Permissions-Policy]]] to
+ are interoperability issues with relying on the [[[Permissions-Policy]]] to
enable the API in third-party contexts. In particular, although
the[^iframe/allow^] attribute is widely supported, the updated syntax
for the [^iframe/allow^] attribute is not. Similarly, the
@@ -713,9 +713,9 @@
the Web Share API in third-party contexts.
- The Working Group expects to make the `Permissions-Policy` HTTP - header mandatory in a future revisions of this specification, once - the header is more widely supported. + When the `Permissions-Policy` HTTP header is more widely supported, + the Working Group expects to revise this specification + to require support for the header.