From 8b370ee9768314d828dbb2996d82a9e437ede9aa Mon Sep 17 00:00:00 2001 From: Fuqiao Xue Date: Thu, 3 Sep 2020 22:07:19 +0800 Subject: [PATCH] Rename Feature Policy to Permissions Policy (#475) See https://github.com/w3c/webappsec-permissions-policy/pull/379 for more info --- data/feature-policy.json | 7 ------- data/permissions-policy.json | 7 +++++++ js/translations.zh.json | 2 +- mobile/security.html | 4 ++-- mobile/security.zh.html | 4 ++-- 5 files changed, 12 insertions(+), 12 deletions(-) delete mode 100644 data/feature-policy.json create mode 100644 data/permissions-policy.json diff --git a/data/feature-policy.json b/data/feature-policy.json deleted file mode 100644 index 8146e986..00000000 --- a/data/feature-policy.json +++ /dev/null @@ -1,7 +0,0 @@ -{ - "url": "https://w3.org/TR/feature-policy-1/", - "impl": { - "caniuse": "feature-policy", - "chromestatus": 5694225681219584 - } -} diff --git a/data/permissions-policy.json b/data/permissions-policy.json new file mode 100644 index 00000000..5399549e --- /dev/null +++ b/data/permissions-policy.json @@ -0,0 +1,7 @@ +{ + "url": "https://www.w3.org/TR/permissions-policy-1/", + "impl": { + "caniuse": "permissions-policy", + "chromestatus": 5745992911552512 + } +} diff --git a/js/translations.zh.json b/js/translations.zh.json index ec68a117..1d45e9c8 100644 --- a/js/translations.zh.json +++ b/js/translations.zh.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": "指针事件", diff --git a/mobile/security.html b/mobile/security.html index 16acefd0..1d17c24d 100644 --- a/mobile/security.html +++ b/mobile/security.html @@ -62,8 +62,8 @@

Technologies in progress

The User Interface Security and the Visibility API 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.

-
-

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 Feature Policy defines mechanisms (the Feature-Policy HTTP header and the allow attribute on an iframe 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.

+
+

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 Permissions Policy defines mechanisms (the Permissions-Policy HTTP header and the allow attribute on an iframe 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.

diff --git a/mobile/security.zh.html b/mobile/security.zh.html index 03b86301..d70394ef 100644 --- a/mobile/security.zh.html +++ b/mobile/security.zh.html @@ -63,8 +63,8 @@

开发中的技术

用户界面安全性和可见性 API 文档建议通过确保图形渲染级别的元素可见性来消除点击劫持。例如，一个开发者部署它可以确保用户点击他们的网站的“支付”按钮不被欺骗，而不会把他们的银行余额转移给冒名顶替者。

-
-

随着更强大的特性不断地暴露在应用中，站点作者需要更加细化地控制应用中启用/禁用的特性，以及应用可以嵌入（在 iframe 中）的自己或第三方的内容，以增强安全性。特性策略定义了一种选择性地启用和禁用各种浏览器特性和API的机制（Feature-Policy HTTP头和 iframe 元素的 allow 属性）。开发者还可以使用该策略对客户端或嵌入者的某些特性和 API 的使用（或缺乏）作出承诺。

+
+

随着更强大的特性不断地暴露在应用中，网站需要更精细地控制应用中启用/禁用的特性，以及应用可以嵌入（在 iframe 中）的自己的或来自第三方的内容，以增强安全性。权限策略定义了一种选择性地启用和禁用各种浏览器特性和 API 的机制（Permissions-Policy HTTP头和 iframe 元素的 allow 属性）。开发者还可以使用该策略对客户端或嵌入者的某些特性和 API 的使用（或缺乏）作出承诺。