Add power-user keyboard mode for ChromeOS with Search key acting as a typical Fn key.

chrome/browser/ui/ash/chrome_shell_delegate.cc

Index: chrome/browser/ui/ash/chrome_shell_delegate.cc
diff --git a/chrome/browser/ui/ash/chrome_shell_delegate.cc b/chrome/browser/ui/ash/chrome_shell_delegate.cc
index ac6e6371b2ce2708feebd9b0907d6eaca7d486ef..776ff3f3e670d4d94f4d58dd44cb34f24d468d2f 100644
--- a/chrome/browser/ui/ash/chrome_shell_delegate.cc
+++ b/chrome/browser/ui/ash/chrome_shell_delegate.cc
@@ -490,6 +490,21 @@ aura::client::StackingClient* ChromeShellDelegate::CreateStackingClient() {
   return new ash::StackingController;
 }
 
+bool ChromeShellDelegate::IsSearchKeyActingAsFunctionKey() const {
+#if defined(OS_CHROMEOS)
+  bool chromebook_function_key = CommandLine::ForCurrentProcess()->HasSwitch(
+      switches::kEnableChromebookFunctionKey);
+  if (!chromebook_function_key)
+    return false;
+
+  Profile* profile = ProfileManager::GetDefaultProfile();
+  return profile->GetPrefs()->GetBoolean(
+      prefs::kLanguageSearchKeyActsAsFunctionKey);

[sky, 2012/11/27 02:01:53]

Is there a reason to have both the flag and the pref? Can't we go with just the
flag for now?

[danakj, 2012/11/27 02:27:18]

Yeh, I was requested to do it this way so that we can have a path to enabling
the feature as:
1. Try out the feature in default-off state.
2. Flip it to default-on and wait until it gets to stable.
3. Remove the flag.

The pref UI is part of the stuff to be "tried out" in step 1.

+#else
+  return false;
+#endif
+}
+
 void ChromeShellDelegate::Observe(int type,
                                   const content::NotificationSource& source,
                                   const content::NotificationDetails& details) {