Reland "[User Education] Clear recent session data when user clears history"

This reverts commit 36a24a7a044d579c537bb6d3fe85e77f9703288e.

Reason for revert: Fixed how prefs were cleared.

Original change's description:
> Revert "[User Education] Clear recent session data when user clears history"
>
> This reverts commit 6415a4e3999d4fe5b0a222ba16ab9e2a13448309.
>
> Reason for revert: Wrong approach was taken, which could lead to
> spurious creation of a service on profile shutdown and (even in the
> best case) cause tests to fail; see attached bug.
>
> Bug: 355249352
>
> Original change's description:
> > [User Education] Clear recent session data when user clears history
> >
> > As requested by privacy review.
> >
> > Exactly what it says on the tin. When the user clears some of their
> > browsing history, the User Education session log (which is used for
> > recording usage telemetry and for triggering certain help bubbles) is
> > fully cleared.
> >
> > Partial clearing is not possible as deleting part of the record would
> > make the data inaccurate.
> >
> > Bug: 349399002
> >
> > Change-Id: Iaafaf07b7ef69bc7ff14afc0daec8196b8bff539
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5734733
> > Commit-Queue: Dana Fried <dfried@chromium.org>
> > Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
> > Reviewed-by: Ayu Ishii <ayui@chromium.org>
> > Reviewed-by: Mariam Ali <alimariam@google.com>
> > Cr-Commit-Position: refs/heads/main@{#1332414}
>
> Bug: 349399002
> Change-Id: I09942395b2e6828cc874f85826163aa3335d279b
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5738606
> Reviewed-by: Ayu Ishii <ayui@chromium.org>
> Reviewed-by: Alison Gale <agale@chromium.org>
> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
> Auto-Submit: Dana Fried <dfried@chromium.org>
> Commit-Queue: Ayu Ishii <ayui@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1332543}

Bug: 355249352
Bug: 349399002
Change-Id: Id2806897be3e4f296777e3abb944538d8855a0d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5739196
Auto-Submit: Dana Fried <dfried@chromium.org>
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Reviewed-by: Mariam Ali <alimariam@google.com>
Commit-Queue: Mariam Ali <alimariam@google.com>
Cr-Commit-Position: refs/heads/main@{#1333466}
4 files changed
tree: 1711dd2b8503f1bfa1973f2606c2c6c6a9813814
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. WATCHLISTS
README.md

Logo Chromium

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.