Resource Timing: Expose firstInterimResponseStart #37984
Merged
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.
This adds an entry to PerformanceResourceTiming:
It also changes the meaning of responseStart to be the first
non-informational header (non-103).
Implemented for Quic, Spdy and HTTP.
All behind a feature runtime flag (ResourceTimingInterimResponseTimes)
Spec issue: w3c/resource-timing#345
Bug: 1402089
Change-Id: I2f050788515959e3576f3cf2bd8df13ff848090a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4165825
Reviewed-by: Bence Béky <[email protected]>
Commit-Queue: Noam Rosenthal <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1094571}