Browser tag shim

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 8888066b84f79a0e97064f745980bb039d5ebe1e..a796c273018678ee43ab1ba700eaf239d53489ca 100644
--- a/chrome/common/extensions/api/_permission_features.json
+++ b/chrome/common/extensions/api/_permission_features.json
@@ -35,6 +35,10 @@
     "channel": "stable",
     "extension_types": ["extension", "packaged_app"]
   },
+  "browserTag": {
+    "channel": "dev",
+    "extension_types": ["platform_app"]

[Aaron Boodman, 2012/07/02 20:52:35]

Before we launch all this stuff, we should talk about philosophy about what goes
in platform apps only.

Right now I am having trouble imagining anything that should be platform-apps
only... but maybe there is some reason why that should not be the case?

[Mihai Parparita -not on Chrome, 2012/07/02 22:05:14]

I don't have a strong preference. The rationale with some of the other APIs
(socket, serial) was that they were scary enough that we'd want to roll them out
gradually. That doesn't seem applicable here.

I've enabled this for extensions too.

[Aaron Boodman, 2012/07/02 23:04:37]

Agree about the rolling out gradually sentiment :). But I think that eventually
we probably want serial, socket, etc to work in extensions.

+  },
   "browsingData": {
     "channel": "stable",
     "extension_types": ["extension", "packaged_app"]