Extend contextMenus API to support browser/page actions

chrome/common/extensions/api/web_view_internal.json

Index: chrome/common/extensions/api/web_view_internal.json
diff --git a/chrome/common/extensions/api/web_view_internal.json b/chrome/common/extensions/api/web_view_internal.json
index 94bf1802ddb0cc1dd6aa49b0402015ee2fb64d47..c09c1261be3e8eecf71c7411cdef64cc855b966c 100644
--- a/chrome/common/extensions/api/web_view_internal.json
+++ b/chrome/common/extensions/api/web_view_internal.json
@@ -124,7 +124,7 @@
                 "items": {
                   "type": "string",
                   // |launcher| isn't actually supported, this is listed here so that we can build |contexts| using the same code from chrome.contextMenus API.
-                  "enum": ["all", "page", "frame", "selection", "link", "editable", "image", "video", "audio", "launcher"]
+                  "enum": ["all", "page", "frame", "selection", "link", "editable", "image", "video", "audio", "launcher", "browser_action", "page_action"]

[Yoyo Zhou, 2014/07/15 23:35:01]

These don't make sense for webviews because:

Webviews are a means by which Chrome apps can embed a frame of web content. The
webview context menus are so the app can specify custom menu elements in that
frame. Since it's an app, it by necessity doesn't have a page or browser action
(and neither does the webview itself).

[gpdavis, 2014/07/16 01:11:10]

Ah, I see.  That makes sense.  The only problem I run into with this is in
context_menus_api_helpers.h; there's an issue regarding templates that arises
when this array is different from the one in context_menus.json.  Without adding
these here, the logic would need to be set up to accommodate for these
differences.  Should I go ahead and make that change, or leave these here in
this json file along with a comment?

                 },
                 "minItems": 1,
                 "optional": true,
@@ -218,7 +218,7 @@
                 "items": {
                   "type": "string",
                   // |launcher| isn't actually supported, this is listed here so that we can build |contexts| using the same code from chrome.contextMenus API.
-                  "enum": ["all", "page", "frame", "selection", "link", "editable", "image", "video", "audio", "launcher"]
+                  "enum": ["all", "page", "frame", "selection", "link", "editable", "image", "video", "audio", "launcher", "browser_action", "page_action"]
                 },
                 "minItems": 1,
                 "optional": true,