|
|
DescriptionUse monotonic time instead of current time in autoscroll controller
Use of a wall clock to drive an animation is dangerous. We should be using the monotinic time.
BUG=645098
Committed: https://crrev.com/7d69521b65cd8d03eabe16411c7198dd1520d382
Cr-Commit-Position: refs/heads/master@{#417365}
Patch Set 1 #
Total comments: 2
Messages
Total messages: 16 (9 generated)
The CQ bit was checked by sunyunjia@chromium.org to run a CQ dry run
Description was changed from ========== Use monotonic time instead of current time in autoscroll controller Use of a wall clock to drive an animation is dangerous. We should be using the monotinic time. BUG=645098 ========== to ========== Use monotonic time instead of current time in autoscroll controller Use of a wall clock to drive an animation is dangerous. We should be using the monotinic time. BUG=645098 ==========
sunyunjia@chromium.org changed reviewers: + bokan@chromium.org, dtapuska@chromium.org
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
PTAL. Thanks!
https://codereview.chromium.org/2326643002/diff/1/third_party/WebKit/Source/c... File third_party/WebKit/Source/core/page/AutoscrollController.cpp (right): https://codereview.chromium.org/2326643002/diff/1/third_party/WebKit/Source/c... third_party/WebKit/Source/core/page/AutoscrollController.cpp:245: if (WTF::monotonicallyIncreasingTime() - m_dragAndDropAutoscrollStartTime > autoscrollDelay) You are going to have to adjust the initialization of the m_dragAndDropAutoscrollStartTime because they are a different clock base (start time).
lgtm https://codereview.chromium.org/2326643002/diff/1/third_party/WebKit/Source/c... File third_party/WebKit/Source/core/page/AutoscrollController.cpp (right): https://codereview.chromium.org/2326643002/diff/1/third_party/WebKit/Source/c... third_party/WebKit/Source/core/page/AutoscrollController.cpp:245: if (WTF::monotonicallyIncreasingTime() - m_dragAndDropAutoscrollStartTime > autoscrollDelay) On 2016/09/08 18:09:51, dtapuska wrote: > You are going to have to adjust the initialization of the > m_dragAndDropAutoscrollStartTime because they are a different clock base (start > time). Nevermind it appears that the m_dragAndDropAutoscrollStartTime is coming from the event timestamp which is monotonic already.
lgtm
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by sunyunjia@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Use monotonic time instead of current time in autoscroll controller Use of a wall clock to drive an animation is dangerous. We should be using the monotinic time. BUG=645098 ========== to ========== Use monotonic time instead of current time in autoscroll controller Use of a wall clock to drive an animation is dangerous. We should be using the monotinic time. BUG=645098 ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Use monotonic time instead of current time in autoscroll controller Use of a wall clock to drive an animation is dangerous. We should be using the monotinic time. BUG=645098 ========== to ========== Use monotonic time instead of current time in autoscroll controller Use of a wall clock to drive an animation is dangerous. We should be using the monotinic time. BUG=645098 Committed: https://crrev.com/7d69521b65cd8d03eabe16411c7198dd1520d382 Cr-Commit-Position: refs/heads/master@{#417365} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/7d69521b65cd8d03eabe16411c7198dd1520d382 Cr-Commit-Position: refs/heads/master@{#417365} |