Add tangentialPressure and twist properties to PointerEvent on Windows

ui/events/blink/web_input_event.cc

Index: ui/events/blink/web_input_event.cc
diff --git a/ui/events/blink/web_input_event.cc b/ui/events/blink/web_input_event.cc
index b423f466b73167a7d9a497fb4048afcd828004f4..f2b364fedd515dd5ffe82530c1bcdfcef56e6be0 100644
--- a/ui/events/blink/web_input_event.cc
+++ b/ui/events/blink/web_input_event.cc
@@ -427,6 +427,8 @@ blink::WebMouseEvent MakeWebMouseEventFromUiEvent(const MouseEvent& event) {
   webkit_event.tiltX = roundf(event.pointer_details().tilt_x);
   webkit_event.tiltY = roundf(event.pointer_details().tilt_y);
   webkit_event.force = event.pointer_details().force;
+  webkit_event.tangentialPressure = event.pointer_details().tangentialPressure;

[mustaq, 2017/01/23 20:23:56]

I think it's better to clamp the incoming values as you did in
web_input_event_builders_mac.mm, to avoid passing on out of bound values from
device drivers.

[lanwei, 2017/01/25 15:53:51]

https://msdn.microsoft.com/en-us/library/windows/desktop/hh454909(v=vs.85).aspx
Windows clearly states that the rotation(twist) is in the range of [0,359]. I
feel it is better to check the range when we get the data from the low level
event from OS. What do you think?

[mustaq, 2017/01/25 16:48:53]

I remember seeing a DCHECK failure for an old Android device in a similar case
for touch. Wanted to avoid the same in case some bad driver is not following the
spec.

I am fine either ways since the spec is clear.

+  webkit_event.twist = event.pointer_details().twist;
   webkit_event.pointerType =
       EventPointerTypeToWebPointerType(event.pointer_details().pointer_type);