Extend input protector to cover key events for permission prompts This change extends input protector to also cover key events (EventType::kKeyPressed and EventType::kKeyReleased) for permission relevant prompts, in order to prevent unintentional key event actions. Also disable input event protection for affected interactive tests that perform automated button press. This is done to prevent the tests from having to wait for the input protector timeout interval. Bug: 364508693, 373794472, 416364499 Change-Id: I590074221366930c5af653554ae3d21d8191f883 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6614637 Reviewed-by: Mitsuru Oshima <oshima@chromium.org> Reviewed-by: Keren Zhu <kerenzhu@chromium.org> Reviewed-by: Florian Jacky <fjacky@chromium.org> Reviewed-by: Lily Chen <chlily@chromium.org> Commit-Queue: Benjamin Keen <bkeen@google.com> Reviewed-by: Zachary Tan <tanzachary@chromium.org> Reviewed-by: Luke Klimek <zgroza@chromium.org> Reviewed-by: Slobodan Pejic <slobodan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1472055}
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.