ref(core): Remove dependence between performance.timeOrigin and performance.timing.navigationStart
#18710
+17
−45
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.
The
performance.timeOriginHighResTimestamp replacedperformance.timing.navigationStarta while ago. I believe we can simplify our timeOrigin determination logic by fully decoupling both values. Previously, we'd only taketimeOriginifnavigationStartwas "more reliable" (less delta toDate.now()). SincetimeOriginhas sub-millisecond precision, this leads to cases where we'd incorrectly take the older, less precisenavigationStartentry, simply becausetimeOriginhad a couple of decimal numbers.Not the end of the world, but this cleans up the code a bit and also reduces some bytes.