summaryrefslogtreecommitdiffstats
path: root/chromium/docs/website/site/Home/chromium-security/enamel/permissions/index.md
diff options
context:
space:
mode:
Diffstat (limited to 'chromium/docs/website/site/Home/chromium-security/enamel/permissions/index.md')
-rw-r--r--chromium/docs/website/site/Home/chromium-security/enamel/permissions/index.md21
1 files changed, 0 insertions, 21 deletions
diff --git a/chromium/docs/website/site/Home/chromium-security/enamel/permissions/index.md b/chromium/docs/website/site/Home/chromium-security/enamel/permissions/index.md
deleted file mode 100644
index 5c3735f75d8..00000000000
--- a/chromium/docs/website/site/Home/chromium-security/enamel/permissions/index.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-breadcrumbs:
-- - /Home
- - Chromium
-- - /Home/chromium-security
- - Chromium Security
-- - /Home/chromium-security/enamel
- - Security UX
-page_name: permissions
-title: Permissions
----
-
-## Testing New Permissions
-
-It's important to test new permissions adequately to ensure they behave as
-expected and regressions are caught. Features that have permissions tend to be
-privacy or security sensitive and if there are circumstances where a malicious
-website can access the feature without adequate user approval it can have a
-particularly negative impact. Please see [Testing New
-Permissions](https://docs.google.com/a/chromium.org/document/d/1daQk9A05T0BcSMO9KQQN8x0TdT2a23KqAkS7maIUJT0/edit?usp=drive_web)
-for important test cases to consider when adding new permissions. \ No newline at end of file