Reset MouseWheelPhaseHandler state when trackpoint scroll is detected

Background:
* TrackPoint does not issue the FlingCancel/FlingStart events, and
  relies on a Timer to fire GestureScrollEnd events.
* Meanhile, TouchPad does issue both events, and MouseWheelPhaseHandler
  detects detects FlingCancel events, it starts the state machine and
  will never start the timer.

How the issue happens:
The bug happens when a user starts scrolling using TrackPoint + middle
mouse, the user's finger may also touch the touchpad, which is
directly below the middle button, which in turn generate FlingCancel
events. As a result, MWPH's state enter TouchPad processing path, and
will never produce ScrollEnd events.

This creates a situation that from Blink point of view, scroll is still going, and it keeps sending scroll events to the element
where scroll started, even if a user release the button and moved to
another element.

How this fix works:
This CL fix it by finding out if the pointer device can generate Fling
events, and resets the state if it's not (TrackPoint).

Bug: 373441235
Test: covered by unittest.

Change-Id: Ibcb73c66b2463f16b37887e3fdee936216b8df57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6772346
Reviewed-by: Zoraiz Naeem <zoraiznaeem@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1494338}
7 files changed
tree: 91526fd3ffb8d9ee80a8fe442e01d65d92c99947
  1. .github/
  2. agents/
  3. android_webview/
  4. apps/
  5. ash/
  6. base/
  7. build/
  8. build_overrides/
  9. buildtools/
  10. cc/
  11. chrome/
  12. chromecast/
  13. chromeos/
  14. codelabs/
  15. components/
  16. content/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia_web/
  23. gin/
  24. google_apis/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. net/
  33. pdf/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .cursorignore
  53. .geminiignore
  54. .git-blame-ignore-revs
  55. .gitallowed
  56. .gitattributes
  57. .gitignore
  58. .gitmodules
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython3
  63. .yapfignore
  64. ATL_OWNERS
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. CPPLINT.cfg
  70. CRYPTO_OWNERS
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. SECURITY_OWNERS
  81. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.