[Privacy Sandbox] Deprecate w/ issue privacySandboxEnabled extension API This CL deprecates the existing privacySandboxEnabled Chrome Extension API with a Chrome DevTools Issue rather than a message on the DevTools Console. See a screen recording of the reported Chrome DevTools Issue when an extension uses the deprecated PrivacySandbox API: http://dr/file/d/1CEtNT35EPxeX_WQaR9dZ38rJxEDqgBt8/view Test extension for Privacy Sandbox Extension APIs used: http://dr/file/d/1Wlk3TzECpU7j_23H9UUZxUdSY2UDTMQc/view Experiment #privacy-sandbox-settings-4 was enabled. Bug: 1378703, b/254414152 Change-Id: I95238abab380a54f2a3e2e8d5e47102212251a7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4166933 Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org> Commit-Queue: Filipa Senra <fsenra@google.com> Cr-Commit-Position: refs/heads/main@{#1097503}
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.