Relative branch.... #2
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
...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.
missing the header parsing and wiring.
…rowserSignals. (WICG#1141) * Add renderSize. * Add requested size, add convert algo. * Add requested size, add convert algo. * Add requested size, add convert algo. * Add requested size, add convert algo. * Add requested size, add convert algo. * Update requestedSize. * Update requestedSize. * Update renderSize * Update spec.bs Co-authored-by: qingxinwu <[email protected]> * Update spec.bs Co-authored-by: qingxinwu <[email protected]> * Update spec.bs Co-authored-by: qingxinwu <[email protected]> * Update spec.bs * Update spec.bs * Update spec.bs Co-authored-by: Dominic Farolino <[email protected]> * Update spec.bs Co-authored-by: Dominic Farolino <[email protected]> * Update spec.bs Co-authored-by: Dominic Farolino <[email protected]> * Remove redundant empty lines --------- Co-authored-by: qingxinwu <[email protected]> Co-authored-by: Dominic Farolino <[email protected]>
…de examples. (WICG#1145) * Update FLEDGE.md * Update FLEDGE.md * Update FLEDGE.md * Update FLEDGE.md
…it (WICG#1175) * Spec: split up response validation into two stages, and fix a bug in it 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. * Document WASM behavior. * Elaborate * Fix link, more precise whitespace. * Fix the exists thing + encoding check --------- Co-authored-by: Maks Orlovich <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.