Wrench menu reorg phase 2

chrome/browser/ui/toolbar/wrench_menu_model.cc

Index: chrome/browser/ui/toolbar/wrench_menu_model.cc
diff --git a/chrome/browser/ui/toolbar/wrench_menu_model.cc b/chrome/browser/ui/toolbar/wrench_menu_model.cc
index ca65ad365d4859b9fa42c920590df7dd574c96d3..6a25b5b633d9e2cdd60b99e577b6a0e93555cf9f 100644
--- a/chrome/browser/ui/toolbar/wrench_menu_model.cc
+++ b/chrome/browser/ui/toolbar/wrench_menu_model.cc
@@ -248,6 +248,10 @@ class WrenchMenuModel::HelpMenuModel : public ui::SimpleMenuModel {
 #else
     int help_string_id = IDS_HELP_PAGE;
 #endif
+// Don't display the about menu item on Chrome OS.

[Peter Kasting, 2015/06/17 22:59:43]

Nit: Say why not.

[edwardjung, 2015/06/18 16:52:05]

Done. Although there doesn't seem to a logical reason not to have a direct link
to about. I've asked around our team if it should be reinstated which would
simplify the code.

+#if !defined(OS_CHROMEOS)
+    AddItem(IDC_ABOUT, l10n_util::GetStringUTF16(IDS_ABOUT));
+#endif
     AddItemWithStringId(IDC_HELP_PAGE_VIA_MENU, help_string_id);
     if (browser_defaults::kShowHelpMenuItemIcon) {
       ui::ResourceBundle& rb = ResourceBundle::GetSharedInstance();
@@ -283,11 +287,7 @@ void ToolsMenuModel::Build(Browser* browser) {
     show_create_shortcuts = false;
 #endif
 
-  AddItemWithStringId(IDC_CLEAR_BROWSING_DATA, IDS_CLEAR_BROWSING_DATA);
-  AddItemWithStringId(IDC_MANAGE_EXTENSIONS, IDS_SHOW_EXTENSIONS);
-
-  if (chrome::CanOpenTaskManager())
-    AddItemWithStringId(IDC_TASK_MANAGER, IDS_TASK_MANAGER);
+  AddItemWithStringId(IDC_SAVE_PAGE, IDS_SAVE_PAGE);
 
   if (extensions::util::IsNewBookmarkAppsEnabled()) {
 #if defined(OS_MACOSX)
@@ -305,6 +305,12 @@ void ToolsMenuModel::Build(Browser* browser) {
   } else if (show_create_shortcuts) {
     AddItemWithStringId(IDC_CREATE_SHORTCUTS, IDS_CREATE_SHORTCUTS);
   }
+  AddSeparator(ui::NORMAL_SEPARATOR);
+  AddItemWithStringId(IDC_CLEAR_BROWSING_DATA, IDS_CLEAR_BROWSING_DATA);
+  AddItemWithStringId(IDC_MANAGE_EXTENSIONS, IDS_SHOW_EXTENSIONS);
+
+  if (chrome::CanOpenTaskManager())
+    AddItemWithStringId(IDC_TASK_MANAGER, IDS_TASK_MANAGER);
 
 #if defined(OS_CHROMEOS)
   AddItemWithStringId(IDC_TAKE_SCREENSHOT, IDS_TAKE_SCREENSHOT);
@@ -314,10 +320,8 @@ void ToolsMenuModel::Build(Browser* browser) {
   AddSubMenuWithStringId(IDC_ENCODING_MENU, IDS_ENCODING_MENU,
                          encoding_menu_model_.get());
   AddSeparator(ui::NORMAL_SEPARATOR);
+

[Peter Kasting, 2015/06/17 22:59:43]

Nit: I can't figure out the logic of when this function adds blank lines. 
Before separators?  After?  Everywhere?  Nowhere?  None of these seems to
accurately describe it.  Pick a system and stick with it.

[edwardjung, 2015/06/18 16:52:05]

Reformatted. Blank lines added for each section of the menu structure described
in the function comment. Also reformatted WrenchMenuModel::Build in the same
manner.

   AddItemWithStringId(IDC_DEV_TOOLS, IDS_DEV_TOOLS);
-  AddItemWithStringId(IDC_VIEW_SOURCE, IDS_VIEW_SOURCE);

[Peter Kasting, 2015/06/17 22:59:43]

Why are we removing View Source?  I don't think that makes sense.

[edwardjung, 2015/06/18 16:52:05]

There's a lot more detail reorganisation in the bug thread but an overview:

We're trying to encourage Dev Tools as the entry point for viewing the source,
console and devices.  For Linux and Mac users, the OS level menu still has the
view source item. On all platforms view source is available from right clicking
on a page and the shortcut key. Most developers would use dev tools or know the
right click / shortcut.

Also the total usage of view source in the wrench menu and it was very small
percentage in the overall view source usage and wrench menu clicks.

Current 7 day view source UMA stats for all browsers:
3.32% of total View Source views came from the wrench menu item (54,208)
View source clicks accounts for 0.073% of all wrench menu items.

On Windows: 
3.41% of total view source visits (45,785).
0.067% of total menu clicks.

[Peter Kasting, 2015/06/18 17:16:58]

I'm still concerned about this.

* 3.5% of total View Source visits still seems like a reasonably high amount.
* The Dev Tools don't make it easy for novices like me to figure out how to
"view source", which I do actually need to do on a surprising number of
occasions.  I worry about this being disproportionately difficult for
non-developers.  I think we still want View Source to be easily accessible for
such users.
* Basic CHI principles argue against making a context menu option the only or
primary way of exposing a feature.
* View Source has a great deal of nostalgic and PR value.  Many people view it
as the capability which democratized the web.  Removing it from these menus
could hurt us on these fronts.

I'm normally a big fan of simplifying and streamlining menus, but given that
this is already buried in a submenu, I'm gravely concerned that the potential
costs of removing this particular item outweigh the benefits.  I'd like to not
do this change.  In the limit, I'd like to make it as a completely separate,
experiment-driven change, and collect sufficient stats to see whether users in
the experimental group figure out how to substitute another way of getting to
this, or whether overall usage decreases.  If usage decreases, that seems like
an argument against the change.

[edwardjung, 2015/06/18 17:42:27]

Copying comments here so that ainslie can see the thread.

I agree that it's not easy to navigate dev tools to view the actual source
versus the rendered DOM, I don't know if there could be improvements there. The
UI of dev tools is going through some change down the line but don't know if the
sources panel will get a make over.

I also do still use view source a lot as a lighter and quicker dev tools to for
quick checks, so also agree that for novices who don't know the shortcut, on
Windows / CrOS at least, we can't educate them once the menu item is removed.
 

-  AddItemWithStringId(IDC_DEV_TOOLS_CONSOLE, IDS_DEV_TOOLS_CONSOLE);
-  AddItemWithStringId(IDC_DEV_TOOLS_DEVICES, IDS_DEV_TOOLS_DEVICES);
 
 #if defined(ENABLE_PROFILING) && !defined(NO_TCMALLOC)
   AddSeparator(ui::NORMAL_SEPARATOR);
@@ -904,16 +908,14 @@ void WrenchMenuModel::Build() {
 
   AddSeparator(ui::NORMAL_SEPARATOR);
 
-  AddItemWithStringId(IDC_SHOW_HISTORY, IDS_SHOW_HISTORY);
-  AddItemWithStringId(IDC_SHOW_DOWNLOADS, IDS_SHOW_DOWNLOADS);
-
   if (!browser_->profile()->IsOffTheRecord()) {
     recent_tabs_sub_menu_model_.reset(new RecentTabsSubMenuModel(provider_,
                                                                  browser_,
                                                                  NULL));
-    AddSubMenuWithStringId(IDC_RECENT_TABS_MENU, IDS_RECENT_TABS_MENU,
+    AddSubMenuWithStringId(IDC_RECENT_TABS_MENU, IDS_HISTORY_RECENT_TABS_MENU,
                            recent_tabs_sub_menu_model_.get());
   }
+  AddItemWithStringId(IDC_SHOW_DOWNLOADS, IDS_SHOW_DOWNLOADS);
 
   if (!browser_->profile()->IsGuestSession()) {
     bookmark_sub_menu_model_.reset(new BookmarkSubMenuModel(this, browser_));
@@ -924,7 +926,7 @@ void WrenchMenuModel::Build() {
   CreateZoomMenu();
 
   AddItemWithStringId(IDC_PRINT, IDS_PRINT);
-  AddItemWithStringId(IDC_SAVE_PAGE, IDS_SAVE_PAGE);
+  // AddItemWithStringId(IDC_SAVE_PAGE, IDS_SAVE_PAGE);

[Peter Kasting, 2015/06/17 22:59:43]

In or out, but not in-but-commented-out.

[edwardjung, 2015/06/18 16:52:05]

Done.

   AddItemWithStringId(IDC_FIND, IDS_FIND);
   if (base::CommandLine::ForCurrentProcess()->HasSwitch(
           switches::kEnableDomDistiller))
@@ -955,15 +957,13 @@ void WrenchMenuModel::Build() {
   }
 #endif
 
-// On ChromeOS we don't want the about menu option.
-#if !defined(OS_CHROMEOS)
-  AddItem(IDC_ABOUT, l10n_util::GetStringUTF16(IDS_ABOUT));
-#endif
-
 #if defined(GOOGLE_CHROME_BUILD)
   help_menu_model_.reset(new HelpMenuModel(this, browser_));
   AddSubMenuWithStringId(IDC_HELP_MENU, IDS_HELP_MENU,
                          help_menu_model_.get());
+#elif !defined(OS_CHROMEOS)
+  // Display the about menu item for non Chrome OS and non Google builds.

[Peter Kasting, 2015/06/17 22:59:43]

Why do we have two blocks in this file both dedicated to adding this ABOUT item?

[edwardjung, 2015/06/18 16:52:05]

We moved the 'About' menu item under the help submenu (block above). However on
Chromium builds the help submenu is not displayed so reinstate the menu item at
the top level. 

I've added an extra comment to describe this.

+  AddItem(IDC_ABOUT, l10n_util::GetStringUTF16(IDS_ABOUT));
 #endif
 
 #if defined(OS_CHROMEOS)