Index: chrome/browser/chromeos/preferences.cc |
diff --git a/chrome/browser/chromeos/preferences.cc b/chrome/browser/chromeos/preferences.cc |
index 2e1b505716ef452d39ce026482a1bc9c5d58775c..5cf58d238ca50d8be2c6d8f5efc09b1d2d277965 100644 |
--- a/chrome/browser/chromeos/preferences.cc |
+++ b/chrome/browser/chromeos/preferences.cc |
@@ -233,9 +233,12 @@ void Preferences::RegisterUserPrefs(PrefRegistrySyncable* registry) { |
registry->RegisterIntegerPref(prefs::kLanguageRemapAltKeyTo, |
input_method::kAltKey, |
PrefRegistrySyncable::SYNCABLE_PREF); |
+ // We don't sync the CapsLock remapping pref, since the UI hides this pref |
+ // on certain devices, so syncing a non-default value to a device that |
+ // doesn't allow changing the pref would be odd. http://crbug.com/167237 |
registry->RegisterIntegerPref(prefs::kLanguageRemapCapsLockKeyTo, |
Yusuke Sato
2013/03/22 18:42:21
I think we need to rename kLanguageRemapCapsLockKe
David Roche
2013/03/22 19:17:11
Is changing the pref name really required, since i
|
input_method::kCapsLockKey, |
- PrefRegistrySyncable::SYNCABLE_PREF); |
+ PrefRegistrySyncable::UNSYNCABLE_PREF); |
registry->RegisterIntegerPref(prefs::kLanguageRemapDiamondKeyTo, |
input_method::kControlKey, |
PrefRegistrySyncable::SYNCABLE_PREF); |