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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide hook for getting a high resolution time between time origin and a "time" #87

Closed
annevk opened this issue Apr 8, 2020 · 1 comment · Fixed by #95
Closed

Provide hook for getting a high resolution time between time origin and a "time" #87

annevk opened this issue Apr 8, 2020 · 1 comment · Fixed by #95

Comments

@annevk
Copy link
Member

annevk commented Apr 8, 2020

The DOM Standard currently creates a DOMHighResTimeStamp representing the high resolution time from the time origin to the time of the occurrence that the event is signaling.

"[T]he time of the occurrence that the event is signaling" is really the only thing that the DOM Standard should define here (or callers). The remainder should be a reference to a concept in this document that does the correct thing. I.e., something that "current high resolution time" also builds upon.

@igneel64
Copy link
Contributor

Proposing the "relative high resolution time" definition which would construct the high resolution time based on a specific time input.
Exporting it so the DOM Standard can use it in the proposed way.

igneel64 added a commit to igneel64/hr-time that referenced this issue Sep 15, 2020
igneel64 added a commit to igneel64/hr-time that referenced this issue Sep 15, 2020
igneel64 added a commit to igneel64/hr-time that referenced this issue Sep 15, 2020
igneel64 added a commit to igneel64/hr-time that referenced this issue Sep 15, 2020
igneel64 added a commit to igneel64/hr-time that referenced this issue Sep 15, 2020
igneel64 added a commit to igneel64/hr-time that referenced this issue Sep 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants