commit | 36ba217c0f1808e1b72be2798a50f0e815fc1a9e | [log] [tgz] |
---|---|---|
author | Xinyi Ji <xinyiji@google.com> | Fri Jan 10 21:08:16 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 10 21:08:16 2025 |
tree | e6e8a8e77a19ce575ca1652c86a4669784a8eedc | |
parent | d452131e99c0576c9cceb8b7d5e44047c0e049d0 [diff] |
[EducationalTip] Implement trigger scenarios for quick delete promo card This CL implements the trigger scenarios for the quick delete promo card: 1. The quick delete promo card in the educational tip module only appears when a user clears their history without using the Quick Delete feature or never clears their history in the past 30 days. Two signals, "count_of_clearing_browsing_data" and "count_of_clearing_browsing_data_through_quick_delete," track this. The signals' values are the logging times of the "Privacy.DeleteBrowsingData.Action" histogram with different enums. 2.The quick delete promo card in the educational tip module will only appear if it has not been shown to the user in more than 10 total sessions. A session is defined as each time Chrome is launched. If the promo card is displayed for the first time in the session, the preference flag "ephemeral_pref_counter.quick_delete_promo_counter" is incremented to register one impression. 3. If the user clicks on the quick delete promo card, it will be permanently disabled. A new preference flag, "ephemeral_pref_interacted.quick_delete_promo_interacted", is introduced to track user interaction with the card. Once the card is clicked, the flag is set to true, and the promo card will no longer be displayed. 4. The quick delete promo card in the educational tip module will appear only when the card has not been displayed to the user more than 3 times in 24 hours. To support this, a signal called "quick_delete_shown_count" and the uma histogram "MagicStack.Clank.NewTabPage.Module.TopImpressionV2" are introduced to handle this criteria. Bug: 355015904 Change-Id: Ied7871863fcb6616effd1b131a5a61c3daaa3075 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6129129 Reviewed-by: Xi Han <hanxi@chromium.org> Reviewed-by: Siddhartha S <ssid@chromium.org> Commit-Queue: Xinyi Ji <xinyiji@chromium.org> Cr-Commit-Position: refs/heads/main@{#1404975}
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.