Page actions behave as disableable browser actions when script badges are enabled.

chrome/browser/ui/views/extensions/browser_action_overflow_menu_controller.cc

Index: chrome/browser/ui/views/extensions/browser_action_overflow_menu_controller.cc
diff --git a/chrome/browser/ui/views/extensions/browser_action_overflow_menu_controller.cc b/chrome/browser/ui/views/extensions/browser_action_overflow_menu_controller.cc
index 826c117e7013d5a6ee7cff693c9fc4f6792fda49..e26037be9efe992e56c133b6dfd9e6155411b75d 100644
--- a/chrome/browser/ui/views/extensions/browser_action_overflow_menu_controller.cc
+++ b/chrome/browser/ui/views/extensions/browser_action_overflow_menu_controller.cc
@@ -87,6 +87,11 @@ void BrowserActionOverflowMenuController::CancelMenu() {
   menu_->Cancel();
 }
 
+bool BrowserActionOverflowMenuController::IsCommandEnabled(int id) const {
+  BrowserActionView* view = (*views_)[start_index_ + id - 1];
+  return view->button()->IsEnabled(owner_->GetCurrentTabId());

[not at google - send to devlin, 2012/07/12 01:07:29]

Same comment here and in the GTK code:

ExtensionToolbarModel already knows to ignore events when browser actions are
disabled. Do we need this too? It's just less code to let the model deal with
it.

(otoh if this kind of thing changes the appearance of buttons, or doesn't play a
sound, or is used by some accessibility tool, or whatever...)

[Yoyo Zhou, 2012/07/12 01:33:27]

I seem to recall this changes the appearance of menu items to make them
disabled.

+}
+
 void BrowserActionOverflowMenuController::ExecuteCommand(int id) {
   BrowserActionView* view = (*views_)[start_index_ + id - 1];
   owner_->OnBrowserActionExecuted(view->button());