Adding `content_security_policy` to imageinfo extension.

chrome/common/extensions/docs/examples/extensions/imageinfo/manifest.json

Index: chrome/common/extensions/docs/examples/extensions/imageinfo/manifest.json
diff --git a/chrome/common/extensions/docs/examples/extensions/imageinfo/manifest.json b/chrome/common/extensions/docs/examples/extensions/imageinfo/manifest.json
index 5301bd0005b5a51dfb7b848f971a3265ff7396df..e18d3c1a79ce9ca49350ed641154aa4fe6edb0a5 100644
--- a/chrome/common/extensions/docs/examples/extensions/imageinfo/manifest.json
+++ b/chrome/common/extensions/docs/examples/extensions/imageinfo/manifest.json
@@ -1,6 +1,6 @@
 {
   "name" : "Imageinfo",
-  "version" : "1.0.0",
+  "version" : "1.0.1",
   "description" : "Get image info for images, including EXIF data",
   "background_page" : "background.html",
   "permissions" : [
@@ -14,5 +14,7 @@
     "16" : "imageinfo-16.png",
     "48" : "imageinfo-48.png",
     "128" : "imageinfo-128.png"
-  }
+  },
+  "content_security_policy": "default-src 'self'; connect-src talkingpointsmemo.com"

[abarth-chromium, 2011/10/15 18:23:12]

When you just specify a host name like you've done in connect-src, that inherits
the current scheme, which is chrome-extension.  You probably want to put the
http and https schemes explicitly.

[abarth-chromium, 2011/10/15 18:24:44]

Maybe this is the wrong CSP policy?  I don't really see any references to
talkingpointsmemo in the extension and I'd expect something like img-src *.

[Use mkwst_at_chromium.org plz., 2011/10/15 18:41:26]

I uploaded the wrong patch. :)  I was experimenting on that website to test
things.

+
 }