Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

performance.timeOrigin vs performance.timing.navigationStart #183

Closed
Quadiago opened this issue Oct 26, 2022 · 3 comments
Closed

performance.timeOrigin vs performance.timing.navigationStart #183

Quadiago opened this issue Oct 26, 2022 · 3 comments

Comments

@Quadiago
Copy link

Hi all!

I've been bashing my head at a problem we've started seeing in Chrome 105 and 106 that leads me to the simple question:

What is timeOrigin compared to navigationStart?

Every definition and comment I can find suggests that they are supposed to be the same, but our data (collected through RUM) suggests differently. Manual testing in Chrome also always shows a difference (which is confirmed by this):

image

Any advice would be appreciated.
@yoavweiss
Copy link
Contributor

This is a Chromium bug. Apologies!

@Quadiago
Copy link
Author

Thanks for responding @yoavweiss . But do you mind confirming, at least according to spec, that timeOrigin is supposed to match navigationStart?

@yoavweiss
Copy link
Contributor

It is supposed to match it. See note under https://www.w3.org/TR/navigation-timing-2/#dom-performancetiming-navigationstart

@Quadiago Quadiago mentioned this issue Dec 2, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yoavweiss @Quadiago