@@ -80,7 +80,7 @@ spec:reporting; urlPrefix: https://w3c.github.io/reporting/
80
80
within their application. It can do so by delivering the following HTTP
81
81
response header to define a feature policy:</p>
82
82
<pre>
83
- <a http-header>Feature -Policy</a> : fullscreen 'none' ; geolocation 'none' </pre>
83
+ <a http-header>Permissions -Policy</a> : fullscreen 'none' ; geolocation 'none' </pre>
84
84
<p> By specifying the "<code> 'none' </code> "keyword for the origin list, the
85
85
specified features will be disabled for all browsing contexts, regardless of
86
86
their origin.</p>
@@ -102,7 +102,7 @@ spec:reporting; urlPrefix: https://w3c.github.io/reporting/
102
102
this by delivering the following HTTP response header to define a restricted
103
103
feature policy for Geolocation:</p>
104
104
<pre>
105
- <a http-header>Feature -Policy</a> : geolocation 'self' https://example.com</pre>
105
+ <a http-header>Permissions -Policy</a> : geolocation 'self' https://example.com</pre>
106
106
<p> The <a>allowlist</a> is a list of one or more origins, which can include
107
107
the application's origin, optionally with the keyword "<code> 'self' </code> ",
108
108
and any third-party origin.</p>
@@ -337,11 +337,11 @@ spec:reporting; urlPrefix: https://w3c.github.io/reporting/
337
337
<section>
338
338
<h2 id="delivery">Delivery</h2>
339
339
<section>
340
- <h3 id="feature -policy-http-header-field">Feature -Policy HTTP Header
340
+ <h3 id="permissions -policy-http-header-field">Permissions -Policy HTTP Header
341
341
Field</h3>
342
342
<p> The `<dfn export http-header
343
- id="feature -policy-header"><code> Feature -Policy</code></dfn> ` HTTP
344
- header field can be used in the [=response=] (server to client) to
343
+ id="permissions -policy-header"><code> Permissions -Policy</code></dfn> `
344
+ HTTP header field can be used in the [=response=] (server to client) to
345
345
communicate the <a>feature policy</a> that should be enforced by the
346
346
client.</p>
347
347
<p> The header's value is the <a href="#ascii-serialization"></a> of one or
@@ -720,12 +720,12 @@ partial interface HTMLIFrameElement {
720
720
<ol>
721
721
<li> Abort these steps if the <var> response</var> ’s <a
722
722
for="response"> header list</a> does not contain a [=header=] whose
723
- [=name=] is "<code> Feature -Policy</code> ".
723
+ [=name=] is "<code> Permissions -Policy</code> ".
724
724
</li>
725
725
<li> Let <var> header</var> be the concatenation of the [=value=] s of all
726
726
[=header=] fields in <var> response</var> ’s <a
727
727
for="response"> header list</a> whose name is
728
- "<code> Feature -Policy</code> ", separated by U+002C (,) (according to
728
+ "<code> Permissions -Policy</code> ", separated by U+002C (,) (according to
729
729
[RFC7230, 3.2.2] ).</li>
730
730
<li> Let <var> feature policy</var> be the result of executing <a>Parse
731
731
header from value and origin</a> on <var> header</var> and
@@ -1081,7 +1081,7 @@ partial interface HTMLIFrameElement {
1081
1081
following registration [[!RFC3864]] :</p>
1082
1082
<dl>
1083
1083
<dt> Header field name</dt>
1084
- <dd> Feature -Policy</dd>
1084
+ <dd> Permissions -Policy</dd>
1085
1085
<dt> Applicable protocol</dt>
1086
1086
<dd> http</dd>
1087
1087
<dt> Status</dt>
0 commit comments