Add SW static routing API timing information to resource timing #415
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
|
This is still a draft PR. |
|
I've updated this PR. The fetch-side of change (whatwg/fetch#1832) needs a bit more work (specifically around getting signals), but I think the resource timing side of change is ready to be looked. Let me ask @yoavweiss for opinions and reviews. |
|
The resource-timing parts look good, but I suspect most of the subtleties will be on the Fetch side.. |
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.
This PR adds the resource timing spec changes for Timing information for SW static routing API.
Explainer here: https://github.com/WICG/service-worker-static-routing-api/blob/main/resource-timing-api.md
Preview | Diff