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

Unified Diff: ui/views/win/hwnd_message_handler.cc

Issue 2914023002: Remove LatencyInfo::sequence_number. (May break metrics).
Patch Set: Rebase Created 3 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: ui/views/win/hwnd_message_handler.cc
diff --git a/ui/views/win/hwnd_message_handler.cc b/ui/views/win/hwnd_message_handler.cc
index 01c372801fee23a42f890ab9f3afb54b7d5733d3..bf5487847e2ee81094e07d2440330901b2ca6def 100644
--- a/ui/views/win/hwnd_message_handler.cc
+++ b/ui/views/win/hwnd_message_handler.cc
@@ -2687,7 +2687,7 @@ LRESULT HWNDMessageHandler::HandlePointerEventTypeTouch(UINT message,
ui::GetModifiersFromKeyState(), rotation_angle);
event.latency()->AddLatencyNumberWithTimestamp(
- ui::INPUT_EVENT_LATENCY_ORIGINAL_COMPONENT, 0, 0, event_time, 1);
+ ui::INPUT_EVENT_LATENCY_ORIGINAL_COMPONENT, 0, event_time, 1);
// There are cases where the code handling the message destroys the
// window, so use the weak ptr to check if destruction occured or not.
@@ -2856,7 +2856,6 @@ void HWNDMessageHandler::GenerateTouchEvent(ui::EventType event_type,
event.latency()->AddLatencyNumberWithTimestamp(
ui::INPUT_EVENT_LATENCY_ORIGINAL_COMPONENT,
0,
- 0,
time_stamp,
1);

Powered by Google App Engine
This is Rietveld 408576698