| commit | fdcf817da49ee92fe191981f7525503444f75f83 | |
| author | jdduke <jdduke@chromium.org> | |
| Tue, 12 May 2015 02:17:21 +0000 (11 19:17 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Tue, 12 May 2015 02:18:33 +0000 (12 02:18 +0000) | ||
| tree | 595de5ef0384830f9a5fbe87a6198494c8ebe654 | treesnapshot (tar.gz zip) |
| parent | 5a47aacd7961fbdc875ff4e7c58ee607195dd7a1 | commitdiff |
Be explicit about forcing TouchSelectionController updates
Previously, cached values in the TouchSelectionController would be reset
to force future selection updates. However, these cached values can
actually be used outside of selection update calls, e.g., when force
showing the selection from the current cached values. Instead of
resetting the cached values, simply set a dirty bit that forces an
update, avoiding issues when dealing with the reset values.
BUG=393025
Review URL: https://codereview.chromium.org/1127383007
Cr-Commit-Position: refs/heads/master@{#329325}
Previously, cached values in the TouchSelectionController would be reset
to force future selection updates. However, these cached values can
actually be used outside of selection update calls, e.g., when force
showing the selection from the current cached values. Instead of
resetting the cached values, simply set a dirty bit that forces an
update, avoiding issues when dealing with the reset values.
BUG=393025
Review URL: https://codereview.chromium.org/1127383007
Cr-Commit-Position: refs/heads/master@{#329325}