<webview>: Implement support for package-local chrome-extension:// URLs

chrome/common/extensions/api/_manifest_features.json

Index: chrome/common/extensions/api/_manifest_features.json
diff --git a/chrome/common/extensions/api/_manifest_features.json b/chrome/common/extensions/api/_manifest_features.json
index 81a842778f89046f0dd09a45abd8c14becbcefe3..46e0057815275fc6a0cfa2204fe55212c54753ee 100644
--- a/chrome/common/extensions/api/_manifest_features.json
+++ b/chrome/common/extensions/api/_manifest_features.json
@@ -374,5 +374,13 @@
     "extension_types": [
       "extension", "legacy_packaged_app", "hosted_app"
     ]
+  },
+  "webview_accessible_resources": {

[Matt Perry, 2013/09/24 21:06:54]

Now that I think about it, maybe these should be grouped under a common key.
Then we could make them optional/required as needed. e.g.
  "webview": {
    "accessible_resources": [x, y, z], // required
    "privileged_partitions": [a, b] // also required?
  }

WDYT?

[Fady Samuel, 2013/09/24 23:05:02]

Agreed, that seems cleaner. Done!

+    "channel": "dev",
+    "extension_types": ["platform_app"]
+  },
+  "webview_privileged_partitions": {
+    "channel": "dev",
+    "extension_types": ["platform_app"]
   }
 }