Revert "cros: move TapToClick prefs to ash"
This reverts commit 9f818c41. Reason for revert: https://crbug.com/872786 Original change's description: > cros: move TapToClick prefs to ash > > changes: > * Move kTapToClickEnabled and kOwnerTapToClickEnabled handling to ash > * In this CL, above pref registrations are still in chrome side because > ash side doesn't have device owner info yet. > > TBR=stevenjb@chromium.org > > Bug: 817643 > Test: manual and test coverage > Change-Id: I6b11eb65a40968eada67ebf2e8b4fb3f1f0eaddc > Reviewed-on: https://chromium-review.googlesource.com/1116210 > Commit-Queue: Qiang Xu <warx@google.com> > Reviewed-by: James Cook <jamescook@chromium.org> > Cr-Commit-Position: refs/heads/master@{#570842} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 872786 Test: On another device, sign in with an account and disable touchpad tap-to-click. Then on the target device, complete OOBE with the same account. In the first user session, tapping should not cause clicks. After signing out, tapping should also not cause clicks. Change-Id: I67a67ba51b56bd14e656e332f8f64e219e3f80ef Reviewed-on: https://chromium-review.googlesource.com/1199873Reviewed-by:James Cook <jamescook@chromium.org> Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> Cr-Commit-Position: refs/heads/master@{#588212}
Showing
Please register or sign in to comment