- From: Dave Methvin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 May 2016 13:46:38 +0000
- To: public-pointer-events@w3.org
Hit testing and calling `elementFromPoint` inside the event handler itself are likely of equivalent cost? Both need to work from a clean layout. If you could push hit testing off to be handled for the rare cases where it is actually desired, rather than taking a constant penalty for it to generate transition events, that sounds like a good thing. It also avoids the need to worry about strange cases where elements change size under the pointer while it's captured and moving. An extra arg to `setPointerCapture` for the caller to define whether they wanted transition events would take care of it if you don't want to make the event handler do its own `elementFromPoint`, although the "you may or may not get transition events" aspect of it might not be good from a documentation standpoint? I would lean towards taking transition events out entirely just to keep things simple and predictable. -- GitHub Notification of comment by dmethvin Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/61#issuecomment-217158395 using your GitHub account
Received on Thursday, 5 May 2016 13:48:34 UTC