Make command-zero reset page scale in addition to zoom level

chrome/browser/ui/browser_command_controller.cc

Index: chrome/browser/ui/browser_command_controller.cc
diff --git a/chrome/browser/ui/browser_command_controller.cc b/chrome/browser/ui/browser_command_controller.cc
index d0c8e571aac62fd370a580abd4958056fe40c4e7..ce0b1b978024abea57a3c8fe00b7223548f82937 100644
--- a/chrome/browser/ui/browser_command_controller.cc
+++ b/chrome/browser/ui/browser_command_controller.cc
@@ -1143,8 +1143,9 @@ void BrowserCommandController::UpdateCommandsForZoomState() {
   if (!contents)
     return;
   command_updater_.UpdateCommandEnabled(IDC_ZOOM_PLUS, CanZoomIn(contents));
-  command_updater_.UpdateCommandEnabled(IDC_ZOOM_NORMAL, ActualSize(contents));
   command_updater_.UpdateCommandEnabled(IDC_ZOOM_MINUS, CanZoomOut(contents));
+  // Reset zoom is always enabled because it also resets page scale.
+  command_updater_.UpdateCommandEnabled(IDC_ZOOM_NORMAL, true);

[Avi (use Gerrit), 2015/02/26 20:16:58]

Can we have it be enabled only if _either_ there is a custom zoom or scale? If
there is no zoom or scale, can we have it disabled?

[ccameron, 2015/02/26 20:23:06]

That information is really deep the renderer and can be changed continuously
with pinch-zoom. It would take an enormous amount of IPC traffic to keep them in
sync (not to mention bug-prone plumbing). Is there a downside to having this
command be enabled?

[Nico, 2015/02/26 20:35:22]

You only need to send "is at no pinch" and "is at pinch". That shouldn't need
much traffic?

 }
 
 void BrowserCommandController::UpdateCommandsForContentRestrictionState() {