-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Register source eligible data host when the beacon is initiated
Fenced frame beacons are pending until the reporting script completes running assuming it completes running before the frame that ran the auction is destroyed. Otherwise they hang out in the reporter until the main frame of the frame running the auction is destroyed. Usually the reporting script runs fast. This CL simplifies the interface in AttributionDataHostManager that integrates with FencedFrameReporter. The source eligible data host is registered when the beacon is initiated. In the case that the beacon failed due to data validation or dropped due to reporting script not completed, NotifyFencedFrameReportingBeaconData is invoked with an opaque reporting origin, and AttributionDataHostManager will stop tracking this beacon. Currently the beacons hang out in AttributionDataHostManager in those cases and is a memory leak. Registering source eligible data host when the beacon is initiated ensures that triggers registered on the landing page are buffered properly even if the reporting script completes later than a quick navigation. Bug: 1428040 Change-Id: I9c55a43394a9dd0e73aab5819a777ee059b2b80c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4368332 Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org> Commit-Queue: Nan Lin <linnan@chromium.org> Reviewed-by: Matt Menke <mmenke@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Cr-Commit-Position: refs/heads/main@{#1122415}
- Loading branch information
1 parent
60510d1
commit b4a9672
Showing
11 changed files
with
252 additions
and
134 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 13 additions & 0 deletions
13
content/browser/attribution_reporting/test/mock_attribution_data_host_manager.cc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
// Copyright 2020 The Chromium Authors | ||
// Use of this source code is governed by a BSD-style license that can be | ||
// found in the LICENSE file. | ||
|
||
#include "content/browser/attribution_reporting/test/mock_attribution_data_host_manager.h" | ||
|
||
namespace content { | ||
|
||
MockAttributionDataHostManager::MockAttributionDataHostManager() = default; | ||
|
||
MockAttributionDataHostManager::~MockAttributionDataHostManager() = default; | ||
|
||
} // namespace content |
Oops, something went wrong.