Add support for flagging extensions without privacy practices Add support for displaying extensions in the Extensions Safety Hub that have not disclosed their privacy practices in their CWS listings. Note that this CL uses existing strings for off-store extensions as a placeholder. Once the real strings are finalized, they will be added in a follow-on CL. Bug: b/334110393 Change-Id: I2c4d6b2396db2ee46932f18a6a1e59f198566eaf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5462027 Commit-Queue: Adam Psarouthakis <psarouthakis@google.com> Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org> Reviewed-by: Side YILMAZ <sideyilmaz@chromium.org> Reviewed-by: Anunoy Ghosh <anunoy@chromium.org> Reviewed-by: Richard Chen <richche@google.com> Cr-Commit-Position: refs/heads/main@{#1291912}
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.