Added TapSuppressionController params to gesture configurations

chrome/browser/ui/webui/gesture_config_ui.cc

Index: chrome/browser/ui/webui/gesture_config_ui.cc
diff --git a/chrome/browser/ui/webui/gesture_config_ui.cc b/chrome/browser/ui/webui/gesture_config_ui.cc
index 8f90f0dc53c2cbe7f90b37ff7998ac0a5118a967..6797789ad415568c706e8da56571e473b2f090f2 100644
--- a/chrome/browser/ui/webui/gesture_config_ui.cc
+++ b/chrome/browser/ui/webui/gesture_config_ui.cc
@@ -108,6 +108,17 @@ void GestureConfigUI::SetPreferenceValue(const base::ListValue* args) {
   Profile* profile = Profile::FromWebUI(web_ui());
   PrefService* prefs = profile->GetPrefs();
 

[mohsen, 2013/01/03 15:20:28]

The following part is to add the ability to set integer preference values
through UI.

-  prefs->SetDouble(pref_name.c_str(), value);
+  const PrefService::Preference* pref =
+      prefs->FindPreference(pref_name.c_str());
+  switch (pref->GetType()) {
+    case base::Value::TYPE_INTEGER:
+      prefs->SetInteger(pref_name.c_str(), static_cast<int>(value));

[rjkroege, 2013/01/03 22:42:49]

the type conversion would happen implicitly? Is the default rounding value what
is desired?

[mohsen, 2013/01/04 16:14:22]

The main reason is that I wrote this code similar to what we have in
ResetPreferenceValue() above. Also, I think this is more explicit and shows that
we are converting double to int deliberately. A better option in my opinion is
to use args->GetInteger() for TYPE_INTEGER case and avoid conversions between
double and int at all.

+      break;
+    case base::Value::TYPE_DOUBLE:
+      prefs->SetDouble(pref_name.c_str(), value);
+      break;
+    default:
+      NOTREACHED();
+  }
 }