Rename Feature Policy to Permissions Policy

See w3c/webappsec-permissions-policy#379 for more info

Author: xfq

data/feature-policy.json

@@ -0,0 +1,7 @@
+{
+  "url": "https://www.w3.org/TR/permissions-policy-1/",
+  "impl": {
+    "caniuse": "permissions-policy",
+    "chromestatus": 5745992911552512
+  }
+}

data/permissions-policy.json

@@ -186,7 +186,6 @@
     "Element Timing API": "元素计时 API",
     "Encrypted Media Extensions": "加密媒体扩展",
     "Event Timing API": "事件计时 API",
-    "Feature Policy": "特性策略",
     "Fetch": "Fetch",
     "File API": "文件 API",
     "Frame Timing": "帧计时",
@@ -236,6 +235,7 @@
     "Payment Method: Basic Card": "支付方式：基本卡",
     "Payment Request API": "支付请求API",
     "Performance Timeline": "性能时间线",
+    "Permissions Policy": "权限策略",
     "Permissions": "权限API",
     "Picture-in-Picture": "画中画",
     "Pointer Events": "指针事件",

js/translations.zh.json

@@ -62,8 +62,8 @@ <h2>Technologies in progress</h2>
 
         <p data-feature="Sandboxing">The <a data-featureid="uisecurity">User Interface Security and the Visibility API</a> document proposes to eliminate clickjacking by assuring element visibility at the graphics rendering level. For instance, a developer deploying it can assure that users clicking their site's "pay" button aren't being tricked into transferring their bank balances to an imposter instead.</p>
 
-        <div data-feature="Feature policy">
-          <p>As more powerful features keep being exposed to applications, site authors need more fine-grained control over features that are enabled/disabled in their application as well as in own or third-party content that their application may embed (in iframes), to reinforce security. The <a data-featureid="feature-policy">Feature Policy</a> defines mechanisms (the <code>Feature-Policy</code> HTTP header and the <code>allow</code> attribute on an <code>iframe</code> element) to selectively enable and disable use of various browser features and APIs. Developers may also use the policy to assert a promise to a client or an embedder about the use — or lack of thereof — of certain features and APIs.</p>
+        <div data-feature="Permissions policy">
+          <p>As more powerful features keep being exposed to applications, site authors need more fine-grained control over features that are enabled/disabled in their application as well as in own or third-party content that their application may embed (in iframes), to reinforce security. The <a data-featureid="permissions-policy">Permissions Policy</a> defines mechanisms (the <code>Permissions-Policy</code> HTTP header and the <code>allow</code> attribute on an <code>iframe</code> element) to selectively enable and disable use of various browser features and APIs. Developers may also use the policy to assert a promise to a client or an embedder about the use — or lack of thereof — of certain features and APIs.</p>
         </div>
       </section>
 

mobile/security.html

@@ -63,8 +63,8 @@ <h2>开发中的技术</h2>
 
         <p data-feature="沙盒"><a data-featureid="uisecurity">用户界面安全性和可见性 API</a> 文档建议通过确保图形渲染级别的元素可见性来消除点击劫持。例如，一个开发者部署它可以确保用户点击他们的网站的“支付”按钮不被欺骗，而不会把他们的银行余额转移给冒名顶替者。</p>
 
-        <div data-feature="特性策略">
-            <p>随着更强大的特性不断地暴露在应用中，站点作者需要更加细化地控制应用中启用/禁用的特性，以及应用可以嵌入（在 iframe 中）的自己或第三方的内容，以增强安全性。<a data-featureid="feature-policy">特性策略</a>定义了一种选择性地启用和禁用各种浏览器特性和API的机制（<code>Feature-Policy</code> HTTP头和 <code>iframe</code> 元素的 <code>allow</code> 属性）。开发者还可以使用该策略对客户端或嵌入者的某些特性和 API 的使用（或缺乏）作出承诺。</p>
+        <div data-feature="权限策略">
+            <p>随着更强大的特性不断地暴露在应用中，网站需要更精细地控制应用中启用/禁用的特性，以及应用可以嵌入（在 iframe 中）的自己的或来自第三方的内容，以增强安全性。<a data-featureid="permissions-policy">权限策略</a>定义了一种选择性地启用和禁用各种浏览器特性和 API 的机制（<code>Permissions-Policy</code> HTTP头和 <code>iframe</code> 元素的 <code>allow</code> 属性）。开发者还可以使用该策略对客户端或嵌入者的某些特性和 API 的使用（或缺乏）作出承诺。</p>
         </div>
       </section>