Skip to content
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

Not yet ready: Spec bidder portion of cross-origin trusted signals #1179

Draft
wants to merge 32 commits into
base: main
Choose a base branch
from

Conversation

morlovich
Copy link
Collaborator

@morlovich morlovich commented May 16, 2024

... Might need to squash it on my end as well, the history is a mess


Preview | Diff

Maks Orlovich added 14 commits May 3, 2024 11:06
...to separate struct + routines, since it's a non-trivial piece of
code in the middle of a complicated algorithm, and I am about to make
it a bit more complicated still.
We will need to do checking in two stages for script bodies to get the
proper cross-site seller signals behavior.

While at it, make sure we actually check that the response is a 2xx;
we are not supposed to be trying to use error pages. Also make the WASM
path go through this, too, so it gets this check as well.
This isn't quite yet ready for review, too many prereqs to worry
about. Seller changes not covered since they're more complex.
Trusted bidding signals do not have to be specified, and the fetches
can fail. In those cases, we will pass in null for the argument, while
the current spec didn't really handle them. Null is also passed in
when the requested keys are empty, rather than an empty dict.
@morlovich morlovich marked this pull request as draft May 16, 2024 15:20
@qingxinwu qingxinwu added the spec Relates to the spec label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec Relates to the spec
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants