commit | f09b08c9e5db436e8725d582ca1085981404936d | [log] [tgz] |
---|---|---|
author | Greg Thompson <grt@chromium.org> | Tue Apr 22 18:07:55 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 22 18:07:55 2025 |
tree | 3d40651a2dfbd46e772ca19efe3ebc23197e09e4 | |
parent | 97c9c54037508644626e641ea534766f9e8533df [diff] |
[A11yPerformance] Isolate tests from platform accessibility integration This change introduces ui::AXMode::kFromPlatform: a meta-flag that must always be used in combination with one or more other flags and is never sent to renderers. It indicates that the other flags in its bundle are being applied in response to an interaction with the platform's accessibility integration. This new mode flag is included at all callsites that enable accessibility as a result of inbound calls (e.g., detection of VoiceOver). BrowserAccessibilityState::SetActivationFromPlatformEnabled() is now used in tests to suppress accessibility modes that are set due to interactions from accessibility tools. This allows tests to run reliably even in the face of unexpected inbound calls. The browser can be launched with --disable-platform-accessibility-integration on the command line to perform this same suppression. A new checkbox in chrome://accessibility does the same. Bug: b/371230119 AX-Relnotes: n/a. Change-Id: Ibe90b0c459b2b0a6b5340237a12109747350b289 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6447273 Reviewed-by: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by: Zijie He <zijiehe@google.com> Reviewed-by: Benjamin Beaudry <benjamin.beaudry@microsoft.com> Auto-Submit: Greg Thompson <grt@chromium.org> Reviewed-by: Charlie Reis <creis@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/main@{#1450072}
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.