New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 909708 link

Starred by 1 user
Status: Assigned
Owner:
afakhry@chromium.org
Cc:
kpschoedel@chromium.org
steve...@chromium.org
mastiz@chromium.org
█ tschumann@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Keyboard settings not syncing

Reported by ha...@harrycameron.com, Nov 28 
UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11021.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.76 Safari/537.36
Platform: 11021.56.0 (Official Build) stable-channel eve

Steps to reproduce the problem:
On ChromeOS:
1. Settings > Keyboard > "Caps Lock" = "Escape"
2. Set up new machine

What is the expected behavior?
Keyboard settings are synced.

What went wrong?
Keyboard settings are not synced which is inconsistent with other settings, e.g., Input method, which are synced.

Did this work before? N/A 

Chrome version: 70.0.3538.76  Channel: stable
OS Version: 11021.56.0
Flash Version: 31.0.0.122

Comment 1 by mamir@chromium.org, Dec 3

Labels: Sync-Triaged
Owner: yusukes@chromium.org
Status: Untriaged (was: Unconfirmed)
Hi Yusuke,

Could you please triage this bug?

Thank you,
Mohamed

Comment 2 by yusukes@google.com, Dec 3

Owner: afakhry@chromium.org
afakhry@, please triage.

Comment 3 by afakhry@chromium.org, Dec 3

Cc: steve...@chromium.org kpschoedel@chromium.org
Status: Assigned (was: Untriaged)
This is WAI per the below comment [1]:

  // 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,
      static_cast<int>(ui::chromeos::ModifierKey::kCapsLockKey));

[1]: https://cs.chromium.org/chromium/src/chrome/browser/chromeos/preferences.cc?q=%22We+don%27t+sync+the+CapsLock+remapping+pref,+since+the%22&g=0&l=363-368

However, that comment dates back to the time before we added CapsLock remapping capability based on the existence of an external keyboard (before, it used to depend only on the lack of the flag:  --has-chromeos-keyboard). So, the above comment sounds like obsolete.
►

Sign in to add a comment