According to the spec and this comment, event level reporting on an auction outcome for both seller and buyer should only be done once the winning ad is handed to a Fenced Frame to render. However, we noticed that the reporting is prematurely triggered in runAdAuction() even though the winning ad is not rendered (BUG). This is problematic, especially since there is no way to stop an auction or prevent it from reporting a winner (if any) once it starts.

For example, imagine the scenario that an auction takes too long to finish, the seller might choose to abandon the auction and render a contextually-targeted ad. The abandoned auction will run to to completion, and report the outcome if there is a winning bid, even though the winning interest group ad will not be rendered. This raises challenges: the backend systems might receive conflicting information about whether there is an interest group auction winner or a contextual winner resulting in an inconsistent auction state; knowing which of the two actually rendered and resulted in a billable event becomes ambiguous.

Can Chrome fix this bug so that the event level reporting is only triggered when the winning ad is rendered in a Fenced Frame?