[3PCD] Update recording metrics when tracking protection onboard

This Cl update IsBlockedByThirdPartyDeprecationExperiment
with adding check whether tracking protection is actually onboard. This
means the third party cookie is real blocked. In other words, we only
record blink feature usage metrics when the 3PCD experiment is actual
block third party cookies and some mechanisms have re-enabled the third
party cookie access.

This also change the meaning of some UMA metric like:
PageLoad.Clients.ThirdPartyCookieAccessBlockedByExperiment. Once the
tracking protection is onboard, page load metric observer won't record
any cookie metrics unless some mechanisms re-enable third party cookie
access.

OBSOLETE_HISTOGRAMS=histogram PageLoad.Clients.ThirdPartyCookieAccessBlockedByExperiment is replaced by PageLoad.Clients.TPCD.ThirdPartyCookieAccessBlockedByExperiment2
OBSOLETE_HISTOGRAMS=histogram PageLoad.Clients.TPCD.TPCAccess.BlockedByExperiment.IsAdOrNonAd is replaced by PageLoad.Clients.TPCD.TPCAccess.BlockedByExperiment.IsAdOrNonAd2
OBSOLETE_HISTOGRAMS=histogram PageLoad.Clients.TPCD.AdTPCAccess.BlockedByExperiment is replaced by PageLoad.Clients.TPCD.AdTPCAccess.BlockedByExperiment2


Change-Id: Iafbd196b32342fe2490c577bbdd5dcbd18db4748
Bug: 1494080
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5033124
Commit-Queue: Victor Tan <victortan@chromium.org>
Reviewed-by: John Delaney <johnidel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1227550}
5 files changed
tree: 850fd6db79d74a26392d0fbfbc811d966f510cfb
  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. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.