Skip to content

Make Permissions-Policy HTTP header OPTIONAL #275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 1, 2023
Prev Previous commit
Next Next commit
Update index.html
An editorial fix (the word "issues" was implied but missing), and rewrite last sentence of future spec expectations to improve grammar, remove use of a passive "mandatory" phrase. Feel free to revise that sentence further.
  • Loading branch information
tantek authored Feb 28, 2023
commit 89cf57daf0eafd63b6888b8c6330e6fa79f4dd5d
8 changes: 4 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -703,7 +703,7 @@ <h2>
<p>
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
Expand All @@ -713,9 +713,9 @@ <h2>
the Web Share API in third-party contexts.
</p>
<p>
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.
</p>
</aside>
</section>
Expand Down