commit | 23c1e15ba3ec8a73c6f50079e602559f4b172795 | [log] [tgz] |
---|---|---|
author | Kartar Singh <kartarsingh@google.com> | Fri Jan 31 17:48:41 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 31 17:48:41 2025 |
tree | ef2c6cf2ac465fe9c607d4431fab5541d7e0db9a | |
parent | d92141ba84c28744c6659240aa46bbba0dda2e74 [diff] |
[InputVizard] Do not transfer input when back gesture can be triggered We have predictive back feature on Chromium which uses Android API: OnBackPressedCallback#handleOnBackProgressed, which requires the input sequence to be on Browser for it to receive input. Even without predictive back, any gesture that started within system gesture insets can be taken over by system and converted into a back. Behavior with InputVizard was that the page could be simultaneously scrolled while the back gesture was initiated by system, since the input continued to come even when system back was in progress. With this change we stop transferring sequence over to Viz if the sequence can be converted to back gesture by the system or internally by Chromium. NO_IFTTT=The Lint rule is being added in this change. Bug: 392584461, 392585257 Change-Id: I15b66b60a63e5326bfee8d6747a952a33c121079 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6215270 Commit-Queue: Kartar Singh <kartarsingh@google.com> Reviewed-by: Alexander Timin <altimin@chromium.org> Reviewed-by: Wenyu Fu <wenyufu@chromium.org> Reviewed-by: Stephen Nusko <nuskos@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/main@{#1414208}
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.