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

timeOrigin is not clamped #105

Closed
yoavweiss opened this issue Feb 15, 2021 · 2 comments
Closed

timeOrigin is not clamped #105

yoavweiss opened this issue Feb 15, 2021 · 2 comments

Comments

@yoavweiss
Copy link
Contributor

According to the spec, timeOrigin is not clamped.
While it's not clear if that can be abused, having performance.now() be and timeOrigin be in different resolutions seems confusing, and there's no clear use case for it. I suggest we clamp timeOrigin as well.
@npm1
Copy link
Contributor

npm1 commented Feb 16, 2021

Oh good point! I see that in Chrome it's not being clamped. Using the same clamping mechanism as that for performance.now() sounds good to me

@yoavweiss
Copy link
Contributor Author

Closed by #106

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 @npm1