Update fetch-later quota expectations #57078
Merged
Conversation
This file contains hidden or 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
wpt-pr-bot
approved these changes
Jan 8, 2026
Collaborator
wpt-pr-bot
left a comment
wpt-pr-bot
left a comment
There was a problem hiding this comment.
The review process for this patch is being conducted in the Servo project.
3 tasks
servo-wpt-sync
force-pushed
the
servo_export_41776
branch
from
48fcae2 to
dc27e3d
Compare
Follows the spec updates per whatwg/fetch#1903 It now expects the explicit requested and quota fields. Unfortunately that is sometimes difficult to determine, since it depends on a couple of things such as data type and internal structure. Therefore, where we know exactly the result we hardcode the value. For those where it is less determinate, we use a function to compute at least an upper-/lowerbound. Signed-off-by: Tim van der Lippe <[email protected]>
servo-wpt-sync
force-pushed
the
servo_export_41776
branch
from
dc27e3d to
18f5642
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follows the spec updates per whatwg/fetch#1903
It now expects the explicit requested and quota
fields.
Unfortunately that is sometimes difficult to
determine, since it depends on a couple of things
such as data type and internal structure. Therefore, where we know exactly the result we hardcode the
value. For those where it is less determinate, we
use a function to compute at least an upper-/lowerbound.
Reviewed in servo/servo#41776