Enable automatic abusive notification revocation on TOT Disabling `kSafetyHubAbusiveNotificationRevocation` feature in flaky tests that are failing after being submitted. See these [1,2] for the reverted CLs that attempted to enable the feature by default on TOT. [1] https://chromium-review.googlesource.com/c/chromium/src/+/5819271 [2] https://chromium-review.googlesource.com/c/chromium/src/+/5828043 Bug: 328773301 Change-Id: Ia894afc23262a0191ac1703af0dfab3357a44c81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5833586 Commit-Queue: Sarah Krakowiak <skrakowi@chromium.org> Reviewed-by: Sarah Krakowiak <skrakowi@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/main@{#1350570}
ChromiumChromium 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.