Remove "POINTER_FLAG_INRANGE" flag when filtering hovering touch moves

When we filter the touch move messages which are not in contact with
the digitizer surface with a flag "POINTER_FLAG_INCONTACT", we should
not check for "POINTER_FLAG_INRANGE", because they are not in the
detection range of the screen of the digitizer. This is based on the
messages we get from the smart board touch device.

Bug: 874948
Change-Id: I06bfd9a4048aa9800c59d974548bc8d82375b8ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691150Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#675632}

ui/views/win/hwnd_message_handler.cc

@@ -2999,11 +2999,8 @@ LRESULT HWNDMessageHandler::HandlePointerEventTypeTouch(UINT message,
   // which most likely happens for smart board, we should ignore these events
   // for now. POINTER_FLAG_INCONTACT indicates this pointer is in contact with
   // the digitizer surface, which means pressing the screen.
-  // POINTER_FLAG_INRANGE indicates the pointer is in the detection range of
-  // the screen.
   if ((message == WM_POINTERUPDATE) &&
-      !(pointer_flags & POINTER_FLAG_INCONTACT) &&
-      (pointer_flags & POINTER_FLAG_INRANGE)) {
+      !(pointer_flags & POINTER_FLAG_INCONTACT)) {
     SetMsgHandled(TRUE);
     return 0;
   }