| commit | 1c72f5185c38f1ae91cb0c6f63f6c1e1e204ed6d | [log] [tgz] |
|---|---|---|
| author | Sarah Krakowiak Criel <skrakowi@chromium.org> | Tue Aug 27 14:48:45 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 27 14:48:45 2024 |
| tree | 4ab43ae89ad108f609b0c13601ae1b363ff3acba | |
| parent | 4396c0ba321442ec6493a61ab64d31b3ebb36fbe [diff] |
Enable abusive notification revocation on TOT This CL keeps the fieldtrial config entry for ChromeOS, since this is going to 20% stable before 100% stable (the rest of Desktop platforms/Android are going to 100% stable) While enabling this feature by default, some tests had failures: -`IndexedHostContentSettingsMapTest` disables `kSafetyHubAbusiveNotificationRevocation` by default since there are non-deterministic failures on Android. There is a separate bug to handle this. -The `AddRevokedPermissions` helper of `UnusedSitePermissionsBridgeTest` had a bug and per help from rubindl@, suggested this change -`SafetyHubMenuNotificationServiceTestDisableAutoAbusiveNotificationRevocation` and `UnusedSitePermissionsServiceSafetyHubDisabledTest` needed `kSafetyHubAbusiveNotificationRevocation` to be explicitly disabled. Bug: 328773301 Change-Id: I658bc9470cf963b28289cf2f17eb77ae8d9ca475 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5805184 Reviewed-by: Ted Choc <tedchoc@chromium.org> Commit-Queue: Sarah Krakowiak <skrakowi@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1347360}
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.