summaryrefslogtreecommitdiffstats
path: root/cc/test/begin_frame_args_test.h
diff options
context:
space:
mode:
authoradlr <adlr@chromium.org>2014-09-09 17:58:21 -0700
committerCommit bot <commit-bot@chromium.org>2014-09-10 01:08:26 +0000
commitdc6bae3bdc5154b73600a1180c0a82859b271a3f (patch)
tree67314c1d232e76fc829600cb770d357dbf5ee64e /cc/test/begin_frame_args_test.h
parentbbadba6b25ff7c7fa3cd2656519693b7fae9c5b8 (diff)
downloadchromium_src-dc6bae3bdc5154b73600a1180c0a82859b271a3f.zip
chromium_src-dc6bae3bdc5154b73600a1180c0a82859b271a3f.tar.gz
chromium_src-dc6bae3bdc5154b73600a1180c0a82859b271a3f.tar.bz2
Chrome OS Touchpad Settings: Always update natural scrolling pref.
Natural (aka australian) scrolling occurs outside Chrome in the X11 touchpad driver. Chrome dictates via an inputcontrol script what the value (true/false) should be. The script notes (in the user's homedir) what the last set value is so that added devices get it applied. Unfortunately, what was happening was Chrome would update the pref before the user logged in, so the inputcontrol script couldn't make a note. Later, when a user was logged in and a new device was attached, the script wouldn't know if australian scrolling should be on or off. To fix, we always set australian scrolling whenever we consider sending touchpad value changes to the inputcontrol script. BUG=chromium:406480 TEST=Tested that when user logs in, chrome always sends the current value of natural scrolling to the inputcontrol script. Also tested that changing non-mouse/tp settings doesn't trigger calls to inputcontrol script. Review URL: https://codereview.chromium.org/553153004 Cr-Commit-Position: refs/heads/master@{#294058}
Diffstat (limited to 'cc/test/begin_frame_args_test.h')
0 files changed, 0 insertions, 0 deletions