Require confirmation for writable directory access.

chrome/common/extensions/api/_permission_features.json

Index: chrome/common/extensions/api/_permission_features.json
diff --git a/chrome/common/extensions/api/_permission_features.json b/chrome/common/extensions/api/_permission_features.json
index c5ca17b225a7851e894ad6d89c8ed94e064be631..ea129ff85603fdaf7a3d0fcc6858b041fc823762 100644
--- a/chrome/common/extensions/api/_permission_features.json
+++ b/chrome/common/extensions/api/_permission_features.json
@@ -277,6 +277,10 @@
     "extension_types": ["extension"],
     "whitelist": [ "2FC374607C2DF285634B67C64A2E356C607091C3" ]
   }],
+  "fileSystem.writeDirectory": [{
+    "channel": "trunk",
+    "extension_types": ["platform_app"]
+  }],

[not at google - send to devlin, 2013/09/03 17:07:04]

For the record: [{...}] in these files is equivalent to just {...} so you can
leave out the []s here and for fileSystem.directory.

In any case: for specifying these for-warning-only permissions you don't
currently need an entry in this file. See
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/common/exte...
for example. 

However, when http://crbug.com/280286 is partially in effect, you will.

However #2, I will try and get the arbitrary-install-prompt logic working, and
if so you won't.

So for now I'd suggest you just remove this.

[Sam McNally, 2013/09/04 00:21:30]

Having fileSystem with the [] and a child permission without the [] CHECK fails
at
https://code.google.com/p/chromium/codesearch/#chromium/src/chrome/common/ext....
Done.

[not at google - send to devlin, 2013/09/04 00:23:07]

Oh. I didn't even realised that those complex permissions worked with the child
permission logic.

   "fontSettings": {
     "channel": "stable",
     "extension_types": ["extension", "legacy_packaged_app"]