ResourceTiming: Add finalResponseHeadersStart As per WebPerfWG resolution: - finalResponseHeadersStart is the timing of the 2xx/4xx/5xx response. - responseStart is the timing of a 1xx response, if such exists, or else the timing of the final 2xx/4xx/5xx response. Behind a flag: ResourceTimingFinalResponseHeadersStart See chromestatus: https://chromestatus.com/feature/5158830722514944 Bug: 40251053 Change-Id: Ic48bef692502ab28dc0ddf2e7420b3a5763e2a6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5987770 Reviewed-by: Stefan Zager <szager@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org> Cr-Commit-Position: refs/heads/main@{#1377776}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.