- From: Rick Byers <notifications@github.com>
- Date: Mon, 21 Sep 2015 13:12:47 -0700
- To: whatwg/dom <dom@noreply.github.com>
Received on Monday, 21 September 2015 20:13:14 UTC
Sorry, let's back up a second, I may be jumping to conclusions based on partial discussions elsewhere. Filed #80 to track the larger issue. If we decide to do that, then `timestamp` is no longer an inherent property of the event, but data supplied by the thing that created the event, and as you've argued elsewhere (`TouchEvent.pageX` I think?) all such properties should be settable via the constructor. Eg. imagine a PointerEvents polyfill that generates `pointermove` events from `mousemove` and `touchmove`. If `timestamp` represents the time the input was first received by the OS, then the polyfill should be able to propagate the value from a `mousemove` into a generated `pointermove`. There are other similar non-polyfill scenarios involving any synthetic input event. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/76#issuecomment-142095945
Received on Monday, 21 September 2015 20:13:14 UTC