[ara] Clarify comment for `context_origin` column
Data deletion logic doesn't use this field anymore.
Change-Id: Icd93c88414b3aca371de7427cbd688cdcd4ff89b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5788285
Auto-Submit: John Delaney <johnidel@chromium.org>
Commit-Queue: John Delaney <johnidel@chromium.org>
Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org>
Commit-Queue: Andrew Paseltiner <apaseltiner@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1341697}
diff --git a/content/browser/attribution_reporting/attribution_storage_sql.cc b/content/browser/attribution_reporting/attribution_storage_sql.cc
index 90cbdfb..451b91e 100644
--- a/content/browser/attribution_reporting/attribution_storage_sql.cc
+++ b/content/browser/attribution_reporting/attribution_storage_sql.cc
@@ -1864,10 +1864,10 @@
// trigger was registered, and should be used for clearing site data.
// |report_time| is the time a <report, source> pair should be
// reported, and is specified by |delegate_|.
- // |context_origin| is the origin that secondarily owns the report for
- // data-deletion purposes. For real reports, it is the destination origin on
- // which the trigger was registered. For fake reports, it is the source
- // origin.
+ // |context_origin| is the origin where the report was created. For
+ // real reports and null reports, it is the destination origin on which the
+ // trigger was registered. For fake event-level reports, it is the source
+ // origin. Used for checking settings and included in aggregatable reports.
// |reporting_origin| is the reporting origin for the report and is the same
// as the |reporting_origin| of its associated source.
// |report_type| indicates whether it's an event-level or aggregatable report.
