[M137] [InputVizard] Use down time to account for transfer time in latency

Original change's description:
> [InputVizard] Use down time to account for transfer time in latency
> 
> When a touch sequence is transferred from Browser to Viz, the Viz
> process receives a new down and uses the event time of this newly
> synthesized down event for latency calculations. To account for time
> taken to transfer touch sequence we are using downtime on Viz for
> calculating latency of down event.
> 
> Note: This wouldn't resolve the issue with any pointer downs (that
> happen to occur before Browser had a chance to request touch transfer)
> from having incorrect latency calculations. Since down time is not the
> correct generation time to use for them, so the plan is to handle those
> with this bug where we will be forwarding events from Browser over to
> Viz: https://crbug.com/383307455.
> 
> Bug: 414788518
> Change-Id: I58264ee4dc034ebe9b46c74c6e7474ed398345ee
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6494577
> Reviewed-by: Jonathan Ross <jonross@chromium.org>
> Commit-Queue: Kartar Singh <kartarsingh@google.com>
> Cr-Commit-Position: refs/heads/main@{#1457577}

Bug: 417488679,414788518
Change-Id: I58264ee4dc034ebe9b46c74c6e7474ed398345ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6546641
Auto-Submit: Chrome Cherry Picker <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/7151@{#1021}
Cr-Branched-From: 8e0d32ed6e49a2415b16e5ed402957cac2349ce2-refs/heads/main@{#1453031}
9 files changed
tree: 335ea2c33d8d67e4b2ce0612f7aa029587a95471
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  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. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.