- From: Dave Tapuska via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Feb 2019 18:31:45 +0000
- To: public-pointer-events@w3.org
I think this is awkward because in order to determine if it is a pointerenter/leave/over/out you need to do a hit test. Even if you kept the target at the time the event first was received what element it matched in an older DOM you'd still need to hit test against the current DOM and it might not match a enter/leave/out/over because the layout was manipulated in between then. Associating them with a hit test removes any performance gains that rAF aligned input was designed to address, then ultimately there would be no point in doing rAF aligned input. I believe the raw pointer movement API is ideal for these cases you've identified in 1/2. -- GitHub Notification of comment by dtapuska Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/278#issuecomment-466498929 using your GitHub account
Received on Friday, 22 February 2019 18:31:46 UTC