SourceEventType added to LatencyInfo

ui/events/blink/web_input_event_traits.cc

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "ui/events/blink/web_input_event_traits.h"
 
 #include "base/logging.h"
 #include "base/strings/stringprintf.h"
 
 using base::StringAppendF;
@@ skipping 234 matching lines @@
 }
 
 uint32_t WebInputEventTraits::GetUniqueTouchEventId(
     const WebInputEvent& event) {
   if (WebInputEvent::isTouchEventType(event.type)) {
     return static_cast<const WebTouchEvent&>(event).uniqueTouchEventId;
   }
   return 0U;
 }
 
+// static
+LatencyInfo WebInputEventTraits::CreateLatencyInfoForWebGestureEvent(
+    WebGestureEvent event) {
+  SourceEventType source_event_type = SourceEventType::UNKOWN;
+  if (event.sourceDevice == blink::WebGestureDevice::WebGestureDeviceTouchpad)
+    source_event_type = SourceEventType::WHEEL;
+  else if (event.sourceDevice ==
+           blink::WebGestureDevice::WebGestureDeviceTouchscreen)

[tdresser, 2016/09/12 14:23:08]

I prefer using {} when the condition is multiline (though this isn't technically
required by the style guide, so your call.

[sahel, 2016/09/12 17:02:26]

Done.

[tdresser, 2016/09/12 18:03:44]

Sorry, this means you need {} on the previous clause as well.

"However, if one part of an if-else statement uses curly braces, the other part
must too:"

https://google.github.io/styleguide/cppguide.html#Conditionals

+    source_event_type = SourceEventType::TOUCH;
+  LatencyInfo latency_info(source_event_type);
+  return latency_info;
+}
+
 }  // namespace ui