You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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'.
The text was updated successfully, but these errors were encountered:
https://dom.spec.whatwg.org/#dom-event-timestamp
Tracking discussion from elsewhere (eg. here) about the plan to try to change
Event.timestamp
into aDOMHighResTimestamp
. 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'.The text was updated successfully, but these errors were encountered: