ResourceTiming: firstInterimResponseStart should include 100 responses #39881
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
wpt-pr-bot
approved these changes
May 7, 2023
3 tasks
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-4507473
branch
from
6541cc3
to
82f9ca2
Compare
Amending implementation based on spec change as per review See discussion: w3c/resource-timing#366 Refactored HTTP1 & HTTP2 tests to be flexible as to whether to send 100 response. Bug: 1402089 Change-Id: If47bd5bf25425f9e5a012cd46be99bdaa1ec6969 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4507473 Commit-Queue: Noam Rosenthal <[email protected]> Reviewed-by: Yoav Weiss <[email protected]> Cr-Commit-Position: refs/heads/main@{#1141426}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-4507473
branch
from
82f9ca2
to
004a8d8
Compare
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.
Amending implementation based on spec change as per review
See discussion: w3c/resource-timing#366
Refactored HTTP1 & HTTP2 tests to be flexible as to whether to send
100 response.
Bug: 1402089
Change-Id: If47bd5bf25425f9e5a012cd46be99bdaa1ec6969
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4507473
Commit-Queue: Noam Rosenthal <[email protected]>
Reviewed-by: Yoav Weiss <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1141426}