Add feature to enable/disable Chrome's ADPF usage based on device's SOC OEMs are starting to adopt ADPF, but inconsistently. While they roll out support, we need the ability to experiment and disable our hinting to prevent regressions. The default allowlist contains only "Google", the rollout to other OEMs requires more testing/verification first. Bug: b/371544495 Change-Id: I59e99b3c792d3a8b55beb01fac67219c2d335396 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5909372 Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Commit-Queue: Igor Kraskevich <kraskevich@google.com> Reviewed-by: Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/main@{#1364987}
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.