diff options
| author | miletus@chromium.org <miletus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-11 19:57:33 +0000 |
|---|---|---|
| committer | miletus@chromium.org <miletus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-11 19:57:33 +0000 |
| commit | bcbb9b4e583a1e068871ef591ae7f8590707eca7 (patch) | |
| tree | c8e296dabb7c064d70c45e622cb272905c4f8811 /sync/protocol/proto_value_conversions_unittest.cc | |
| parent | 0fd8941aeaf0de8233cf6b017956217fe7371a32 (diff) | |
| download | chromium_src-bcbb9b4e583a1e068871ef591ae7f8590707eca7.zip chromium_src-bcbb9b4e583a1e068871ef591ae7f8590707eca7.tar.gz chromium_src-bcbb9b4e583a1e068871ef591ae7f8590707eca7.tar.bz2 | |
Keep the oldest LatencyInfo when coalescing input events
Input events can be coalesced at browser side, e.g. GestureScrollUpdate,
before being sent to renderer. Currently when events are coalesced, LatencyInfo
are merged. We want to move to per-event LatencyInfo tracking and get rid
of LatencyInfo merge. It seems reasonable to keep the oldest LatencyInfo, which
when used for input event latency analysis, will represent the longest latency.
BUG=246034
TEST=None
Review URL: https://codereview.chromium.org/86603003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@240160 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync/protocol/proto_value_conversions_unittest.cc')
0 files changed, 0 insertions, 0 deletions