Chromium Code Reviews| 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 ed35c8062943f977f3333daa4211987d3b0b6692..8b25e0766f45040e2e61a27bb9065a3ec63ec1f2 100644 |
| --- a/chrome/common/extensions/api/_permission_features.json |
| +++ b/chrome/common/extensions/api/_permission_features.json |
| @@ -228,6 +228,10 @@ |
| "channel": "stable", |
| "extension_types": ["extension", "packaged_app"] |
| }, |
| + "pushMessaging": { |
| + "channel": "dev", |
| + "extension_types": ["platform_app"] |
|
Munjal (Google)
2012/08/14 18:56:37
I think we should allow this feature for packaged
dcheng
2012/08/14 21:39:59
On #crx, I think Aaron mentioned that all the new
|
| + }, |
| // Note: runtime is not actually a permission, but some systems check these |
| // values to verify restrictions. |
| "runtime": { |