Add suspicious notification id list to website settings To fix a UI bug that only sends 1 warning notification per site (rather than a warning notification for every suspicious notification for the site), the suspicious notification ids need to be persisted. The host content settings map is a good contender because the ids are strings, so this list is lightweight. In future CLs, the suspicious notification ids will be stored and retrieved using the host content settings map. When the user chooses to show all suspicious notifications, the ids will be used to obtain notification contents from the database and display them. Bug: 412379309 Change-Id: I769d2399df773b9c446beb1f1859a9d1f1d0169d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6519953 Commit-Queue: Sarah Krakowiak <skrakowi@chromium.org> Reviewed-by: Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/main@{#1458818}
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.