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

Consider making timestamp a DOMHighResTimestamp #80

Closed
RByers opened this issue Sep 21, 2015 · 2 comments
Closed

Consider making timestamp a DOMHighResTimestamp #80

RByers opened this issue Sep 21, 2015 · 2 comments

Comments

@RByers
Copy link
Contributor

RByers commented Sep 21, 2015

https://dom.spec.whatwg.org/#dom-event-timestamp

Tracking discussion from elsewhere (eg. here) about the plan to try to change Event.timestamp into a DOMHighResTimestamp. In addition to changing the type, what other spec changes are needed?

To me the main value we'd get from timestamp is if it's permitted to carry information about when logically the action occurred (which may be before the "event was created"). This can be used, for example, to get some measure of input event processing latency. WebKit has done this for input events for several years and we've been debating about how to expose this in blink/chromium even longer.

@birtles @majido @tdresser

If we find it's not compatible to make these changes to timestamp then we should still take everything we've learned here and apply it to a new field, eg. `platformTimestamp'.

@annevk
Copy link
Member

annevk commented Sep 22, 2015

This is #23, no?

@RByers
Copy link
Contributor Author

RByers commented Sep 22, 2015

Ah, sorry. I searched for timestamp and so didn't find that one :-)

@RByers RByers closed this as completed Sep 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants