Expose "relative high resolution coarse time" #114
Merged
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
For resource-timing, we pre-coarsen the timestamps before they can be converted to relative timestamps, so the inermediate algorithm to calculate the relative timestamp from a pre-coarsened absolulte timestamp is needed. See w3c/resource-timing#261
npm1
approved these changes
Mar 25, 2021
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.
For resource-timing, we pre-coarsen the timestamps before
they can be converted to relative timestamps, so the inermediate
algorithm to calculate the relative timestamp from a pre-coarsened
absolulte timestamp is needed.
See w3c/resource-timing#261
Preview | Diff