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

Update usage of hr-time "current high resolution time" algorithm #78

Closed
igneel64 opened this issue Sep 22, 2020 · 3 comments · Fixed by #82
Closed

Update usage of hr-time "current high resolution time" algorithm #78

igneel64 opened this issue Sep 22, 2020 · 3 comments · Fixed by #82

Comments

@igneel64
Copy link

Based on the updated "current time high resolution time" on the hr-time spec.

Change the current high resolution time definition to match the new algorithm defined in the hr-time spec.
@skobes-chromium
Copy link
Collaborator

What is the update that needs to be made here?

@npm1
Copy link
Collaborator

npm1 commented Sep 23, 2020

It needs to pass a global object. I think @igneel64 might want to tackle this on the hackathon next Tuesday though so no need to worry about this for now.

@igneel64
Copy link
Author

Seems @npm1 beat me to it, but yes this issue was opened so that we conform to the current high resolution time algorithm requiring a global object to be passed to.
Will be PRed by us most probably 😄

npm1 added a commit that referenced this issue Oct 6, 2020
@npm1
Pass global object to current high res time
619f79c 
Fixes #78
@npm1 npm1 mentioned this issue Oct 6, 2020
Merged
@npm1 npm1 closed this as completed in #82 Oct 6, 2020
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

Successfully merging a pull request may close this issue.

Pass global object to current high res time WICG/layout-instability
3 participants
@skobes-chromium @igneel64 @npm1