-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move lifetimeMs from GenerateBidInterestGroup to AuctionAdInterestGroup #843
Conversation
Move lifetimeMs from GenerateBidInterestGroup to AuctionAdInterestGroup because of concerns about ambiguity and providing a high accuracy timer when executionMode allows multiple same-origin interest groups to share state. Note that lifetimeMs was never provided to generateBid() in Chrome, anyways, so no consumers should be broken by this change.
If there's a need for generateBid() to know the expiry, I think it would be better to provide it browserSignals, where there's no ambiguity and likely to be no confusion over its meaning. More generally, I wonder if we should default to putting fields in AuctionAdInterestGroup unless they're really needed in GenerateBidInterestGroup (e.g., I'm skeptical the priorityVector or enableBiddingSignalsPrioritization are useful). |
At least for now expiry is not used in
Good catch! Yes, that's desirable. I think I put |
I had assumed you put it there because that's what the explainer calls for, and that's what the code currently does. :) |
Yeah your assumption sounds more aligned with why I did that :) |
Looking at the code, the only other thing we don't currently set is executionMode, I believe. |
Move lifetimeMs from GenerateBidInterestGroup to AuctionAdInterestGroup because of concerns about ambiguity and providing a high accuracy timer when executionMode allows multiple same-origin interest groups to share state.
Note that lifetimeMs was never provided to generateBid() in Chrome, anyways, I believe, so no consumers should be broken by this change.
Preview | Diff