- From: Ryc O'Chet via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Aug 2017 10:41:36 +0000
- To: public-pointer-events@w3.org
It's always possible to get the element under the pointer via `window.elementFromPoint` (which could be caching if it's the current mouse pointer position on a per-mouse-move bases) - if someone is wanting a really high speed from the mouse then it's more likely that it'll be using WebGL or Canvas, or interested in the delta rather than the element under it (which is unlikely to change much between rAF based `mouseover` / `mouseenter` events). The only things that are needed from a `MouseEvent` / `TouchEvent` are the position and type - for the mouse it's `pageX` / `pageY` / `which`, but touch has `changedTouches` with a little more detail on it. If gamepads also got added (as an addition to the Gamepad API) then it would likely have yet more attributes (but that would be subject to a different discussion) ;-) -- GitHub Notification of comment by Rycochet Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/214#issuecomment-322158458 using your GitHub account
Received on Monday, 14 August 2017 10:41:37 UTC