commit | 61bbffd76cf0c81645185aa43d431dc88e0ee25e | [log] [tgz] |
---|---|---|
author | Victor Tan <victortan@google.com> | Tue Nov 21 20:00:15 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 21 20:00:15 2023 |
tree | 850fd6db79d74a26392d0fbfbc811d966f510cfb | |
parent | 8aafb2477254e8aeb85009999fc770ef67d5d8c3 [diff] |
[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}
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.