Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(118)

Issue 1127383007: Be explicit about forcing TouchSelectionController updates (Closed)

Created:
5 years, 7 months ago by jdduke (slow)
Modified:
5 years, 7 months ago
Reviewers:
mohsen
CC:
chromium-reviews, Donn Denman
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Reland "Be explicit about forcing TouchSelectionController updates" This change landed in r329325 but was reverted due to an uninitialized member variable. The issue has been fixed. Original description: ---------------------------- 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 Committed: https://crrev.com/da232ee4d57ce8e6a8b3d4f9f2795c06b3720c0f Cr-Commit-Position: refs/heads/master@{#329422}

Patch Set 1 #

Patch Set 2 : Rebase #

Patch Set 3 : Initialize force_next_update_ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+20 lines, -15 lines) Patch
M ui/touch_selection/touch_selection_controller.h View 1 2 chunks +5 lines, -1 line 0 comments Download
M ui/touch_selection/touch_selection_controller.cc View 1 2 8 chunks +12 lines, -14 lines 0 comments Download
M ui/touch_selection/touch_selection_controller_unittest.cc View 1 1 chunk +3 lines, -0 lines 0 comments Download

Messages

Total messages: 16 (5 generated)
jdduke (slow)
mohsen@: PTAL, thanks. donnd@ uncovered this when adding a unit test in crrev.com/1102933003.
5 years, 7 months ago (2015-05-11 21:53:06 UTC) #2
mohsen
LGTM, though you need to rebase because of r329191.
5 years, 7 months ago (2015-05-12 00:26:57 UTC) #3
jdduke (slow)
On 2015/05/12 00:26:57, mohsen wrote: > LGTM, though you need to rebase because of r329191. ...
5 years, 7 months ago (2015-05-12 00:36:43 UTC) #4
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1127383007/20001
5 years, 7 months ago (2015-05-12 00:38:23 UTC) #7
commit-bot: I haz the power
Committed patchset #2 (id:20001)
5 years, 7 months ago (2015-05-12 02:17:28 UTC) #8
commit-bot: I haz the power
Patchset 2 (id:??) landed as https://crrev.com/fdcf817da49ee92fe191981f7525503444f75f83 Cr-Commit-Position: refs/heads/master@{#329325}
5 years, 7 months ago (2015-05-12 02:19:13 UTC) #9
benwells
A revert of this CL (patchset #2 id:20001) has been created in https://codereview.chromium.org/1139533006/ by benwells@chromium.org. ...
5 years, 7 months ago (2015-05-12 04:51:17 UTC) #10
jdduke (slow)
On 2015/05/12 04:51:17, benwells wrote: > A revert of this CL (patchset #2 id:20001) has ...
5 years, 7 months ago (2015-05-12 15:03:01 UTC) #11
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1127383007/40001
5 years, 7 months ago (2015-05-12 15:05:29 UTC) #14
commit-bot: I haz the power
Committed patchset #3 (id:40001)
5 years, 7 months ago (2015-05-12 16:51:49 UTC) #15
commit-bot: I haz the power
5 years, 7 months ago (2015-05-12 16:52:28 UTC) #16
Message was sent while issue was closed.
Patchset 3 (id:??) landed as
https://crrev.com/da232ee4d57ce8e6a8b3d4f9f2795c06b3720c0f
Cr-Commit-Position: refs/heads/master@{#329422}

Powered by Google App Engine
This is Rietveld 408576698