Use new policies to control Device Attributes API access. This commit introduces managing the access to the Device Attributes API with the Content Settings infrastructure. Bug: 372467879 Change-Id: I4d4faf276ab7571c4aa4284220668db91d08336f Low-Coverage-Reason: COVERAGE_UNDERREPORTED Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6632823 Reviewed-by: Sergii Bykov <sbykov@google.com> Reviewed-by: Victor Gabriel Savu <vsavu@google.com> Reviewed-by: Martin Šrámek <msramek@chromium.org> Commit-Queue: Patryk Chodur <pchodur@google.com> Reviewed-by: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1494516}
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.