Allow content script insertion on about:-URLs.

chrome/test/data/extensions/api_test/content_scripts/about_blank_srcdoc/manifest.json

Index: chrome/test/data/extensions/api_test/content_scripts/about_blank_srcdoc/manifest.json
diff --git a/chrome/test/data/extensions/api_test/content_scripts/about_blank_srcdoc/manifest.json b/chrome/test/data/extensions/api_test/content_scripts/about_blank_srcdoc/manifest.json
new file mode 100644
index 0000000000000000000000000000000000000000..e75f7f2f7ef8c336ffb12466e13a87ee1f4ba152
--- /dev/null
+++ b/chrome/test/data/extensions/api_test/content_scripts/about_blank_srcdoc/manifest.json
@@ -0,0 +1,18 @@
+{
+  "name": "about:blank and about:srcdoc",
+  "version": "1.0",
+  "manifest_version": 2,
+  "description": "Tests that content scripts are injected in about:blank and about:srcdoc frames if it has access to the parent frame.",
+  "background": {
+    "page": "test.html"
+  },
+  "permissions": ["*://*/*"],
+  "content_scripts": [
+    {
+      "matches": ["*://*/*"],

[not at google - send to devlin, 2014/04/21 22:34:41]

if you test with "permissions" and "matches" that don't overlap I think you'll
see that bug I mentioned previously.

[robwu, 2014/04/21 23:21:46]

After removing "permissions": ["*://*/*"], the browser tests still pass.

+      "match_about_blank": true,
+      "js": ["content_script.js"],
+      "all_frames": true
+    }
+  ]
+}