From 2e026aae7b5e181eceef579267e4a3c36dac4a77 Mon Sep 17 00:00:00 2001 From: Paul Jensen Date: Mon, 13 Jan 2025 12:38:05 -0500 Subject: [PATCH] Fix stale reference to prevWins in FLEDGE.md --- FLEDGE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FLEDGE.md b/FLEDGE.md index 01c424c6d..81f6dbb51 100644 --- a/FLEDGE.md +++ b/FLEDGE.md @@ -1152,7 +1152,7 @@ _As a temporary mechanism, we will still allow network access,_ rendering the wi The TURTLEDOVE privacy goals mean that this cannot be the long-term solution. Rendering ads from previously-downloaded Web Bundles, as originally proposed, is one way to mitigate this leakage. Another possibility is ad rendering in which all network-loaded resources come from a trusted CDN that does not keep logs of the resources it serves. As with servers involved in providing the trusted bidding signals, the privacy model and browser trust mechanism for such a CDN would require further work. -Reports are only sent and most interest group state changes (e.g. updating `prevWins` and `bidCount`, updating k-anonymity information) are only applied if and when the winning `renderURL` is loaded in a fenced frame, in the case there is a winner, or when there is no winner. Priorities and `priorityOverrides` are updated immediately upon completion of the `generateBid()` call that invoked their respective update functions, since how the information from those are used is not expected to depend on whether the current auction was completed or not. +Reports are only sent and most interest group state changes (e.g. updating `prevWinsMs` and `bidCount`, updating k-anonymity information) are only applied if and when the winning `renderURL` is loaded in a fenced frame, in the case there is a winner, or when there is no winner. Priorities and `priorityOverrides` are updated immediately upon completion of the `generateBid()` call that invoked their respective update functions, since how the information from those are used is not expected to depend on whether the current auction was completed or not. ### 5. Event-Level Reporting (for now)