Add finalResponseHeadersStart docs #37740
Merged
+123
−8
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
tunetheweb
requested review from
sideshowbarker
and removed request for
a team
|
Preview URLs
Flaws (1)Note! 4 documents with no flaws that don't need to be listed. 🎉 URL:
(comment last updated: 2025-01-22 01:50:45) |
files/en-us/web/api/performanceresourcetiming/finalresponseheadersstart/index.md
Outdated
Show resolved
Hide resolved
files/en-us/web/api/performanceresourcetiming/finalresponseheadersstart/index.md
Outdated
Show resolved
Hide resolved
files/en-us/web/api/performanceresourcetiming/finalresponseheadersstart/index.md
Outdated
Show resolved
Hide resolved
sideshowbarker
approved these changes
Jan 22, 2025
|
Cheers! |
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.
Description
Add
finalResponseHeadersStartdocs coming to Chrome in Chrome 133.This also updates the outdated TTFB docs.
Motivation
New header starting to be made available in browsers to clarify the meaning of TTFB.
Additional details
https://chromestatus.com/feature/5158830722514944
Also various discussions in W3C WebPerf WG:
Related issues and pull requests
See also: