commit 159d4de8d182838b468ec92113f714f10626e5dc
author Adam Abeshouse <aabeshouse@google.com> Mon Dec 09 21:27:18 2024
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Mon Dec 09 21:27:18 2024
tree c39d518c2991d632cb55b72584a844500783f2b1
parent e60732b2f176220d86624e6e08619cf1d7f09447

[FPF] Save (but don't act on) breakage exceptions based on refresh heuristic

In previous CLs, we have added code to keep track of user
refreshes per eTLD+1 in a single WebContents, for the purpose
of heuristically detecting breakage due to Fingerprinting
Protection.

Here we check whether the number of refreshes crosses a threshold,
set by the feature flag param `refresh_heuristic_exception_threshold`,
after which we record an exception for the eTLD+1 in a profile pref.

As part of this CL, we also move the refresh heuristic metrics
tracking to DidStartNavigation instead of DidFinishNavigation,
since that's a more natural place to track refresh attempts
due to breakage.

In an upcoming CL, we will read from the profile pref
in order to disable Fingerprinting Protection for sites
that have an exception on record.

Change-Id: Ic06445ad2d23964538c9a8bb5a1f489b9e9a5dd1
Bug: 372669423
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962525
Reviewed-by: Fiona Macintosh <fmacintosh@google.com>
Reviewed-by: Zainab Rizvi <rizvis@google.com>
Reviewed-by: Martin Verde <thesalsa@google.com>
Commit-Queue: Adam Abeshouse <aabeshouse@google.com>
Cr-Commit-Position: refs/heads/main@{#1393885}