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.

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

Already on GitHub? Sign in to your account

馃攰馃悰 [RUMF-201] add internal logs for abnormal timeOrigin #219

Merged
merged 3 commits into from Dec 20, 2019

Conversation

BenoitZugmeyer
Copy link
Member

This will make sure #217 will solve the adnormal timing issue.

This will make sure #217 will
solve the adnormal timing issue.
@BenoitZugmeyer BenoitZugmeyer requested a review from a team as a code owner December 20, 2019 10:38
@BenoitZugmeyer BenoitZugmeyer force-pushed the benoit/log-diff-time-origin-navigation-start branch from 843cda3 to 2d2ba84 Compare December 20, 2019 15:02
@BenoitZugmeyer BenoitZugmeyer merged commit 41e8bce into master Dec 20, 2019
@BenoitZugmeyer BenoitZugmeyer deleted the benoit/log-diff-time-origin-navigation-start branch December 20, 2019 15:15
BenoitZugmeyer added a commit that referenced this pull request Jan 6, 2020
* 馃悰 [RUMF-201] use timing.navigationStart to compute fake timings

Using `performance.timing.navigationStart` instead of
`performance.timeOrigin` has several advantages:

* it is defined on more browsers ;
* it produces timings closer to the real PerformanceNavigationTiming
event ;
* performance.timeOrigin may be far in the past for some reason, causing
abnormal timings.

* Revert "馃攰馃悰 [RUMF-201] add internal logs for abnormal timeOrigin (#219)"

This reverts commit 41e8bce.

* 馃憣馃摑 add a link to the related Firefox issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants