commit | 14f3b4c779583bf11d39b4ed79095063d8b9e4c7 | [log] [tgz] |
---|---|---|
author | Kartar Singh <kartarsingh@google.com> | Wed May 14 23:24:55 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 14 23:24:55 2025 |
tree | 335ea2c33d8d67e4b2ce0612f7aa029587a95471 | |
parent | 1b9a647b2eca413015fafd9e2c0764d37a4481bd [diff] |
[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}
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.