Add support for a "frame" context option to chrome.contextMenus.create/update.

chrome/browser/extensions/extension_context_menu_api.cc

Index: chrome/browser/extensions/extension_context_menu_api.cc
diff --git a/chrome/browser/extensions/extension_context_menu_api.cc b/chrome/browser/extensions/extension_context_menu_api.cc
index d8e93f28a868aa4a542df6f1bd96e323fccb36b9..a9419c740daef5e420a92269e6d81bcca175d2f4 100644
--- a/chrome/browser/extensions/extension_context_menu_api.cc
+++ b/chrome/browser/extensions/extension_context_menu_api.cc
@@ -1,4 +1,4 @@
-// Copyright (c) 2010 The Chromium Authors. All rights reserved.
+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
@@ -65,6 +65,8 @@ bool ExtensionContextMenuFunction::ParseContexts(
       tmp_result.Add(ExtensionMenuItem::VIDEO);
     } else if (value == "audio") {
       tmp_result.Add(ExtensionMenuItem::AUDIO);
+    } else if (value == "frame") {

[asargent_no_longer_on_chrome, 2011/04/06 19:33:10]

Would it make sense to call this "frames" instead of "frame", since it applies
to all frames on a page?

You'll also need to add this to the "contexts" array inside the
"createProperties" parameter of contextMenus' create method in
extension_api.json. 

[Mihai Parparita -not on Chrome, 2011/04/06 19:48:14]

As discussed, all the other context names ("link", "image", etc.) are singular
too, presumably because only one such item will be active/the target when the
menu is shown.
Docs are now updated (I ended up picking up the changes from
http://trac.webkit.org/changeset/83033 too when re-generating).

+      tmp_result.Add(ExtensionMenuItem::FRAME);
     } else {
       error_ = ExtensionErrorUtils::FormatErrorMessage(kInvalidValueError, key);
       return false;