Clean up fake report generation

[linnan-github]

Many fields in the trigger is irrelevant of event-level report generation. Removed fakeTrigger and passed the corresponding fields into the algorithm.

---

Preview | Diff

[apasel422]

I don't think this is correct. Per the Chromium link, it's only the context origin that is set that way, not the actual attribution destinations.

[linnan-github]

I don't think this is correct. Per the Chromium link, it's only the context origin that is set that way, not the actual attribution destinations.

Yeah the fake trigger's destination is not actually not used for the event-level report, but I feel it's easier to understand.

BTW, this needs to be fixed anyways as the destination is a list.

[apasel422]

Yeah the fake trigger's destination is not actually not used for the event-level report, but I feel it's easier to understand.

I disagree: The context origin only really exists as a concept in the Chromium implementation, as it's needed strictly for data deletion and browser policy.

BTW, this needs to be fixed anyways as the destination is a list.

You're right, but maybe the better approach is to stop generating a fake trigger at all in the spec.

[linnan-github]

Yeah the fake trigger's destination is not actually not used for the event-level report, but I feel it's easier to understand.

I disagree: The context origin only really exists as a concept in the Chromium implementation, as it's needed strictly for data deletion and browser policy.

BTW, this needs to be fixed anyways as the destination is a list.

You're right, but maybe the better approach is to stop generating a fake trigger at all in the spec.

Yeah that's fair. Maybe we can update "obtain an event-level report" algorithm to take trigger time and trigger debug key instead of a trigger.