- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Sep 2016 23:46:10 +0000
- To: public-pointer-events@w3.org
Well, our motivation for not wanting explicit capture to send boundary events all the time is the same as #61: we don't want developers to be hit with the hit-test costs on every pointermove unless they've explicitly opted-in to a feature that fundamentally requires it (eg. releasing pointer capture, or asking specifically to be notified when a captured pointer is no longer over top of the capturing node). I'll leave it to @teddink to describe his motivation for preferring to keep boundary events for explicit `setPointerCapture`. -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/143#issuecomment-248161820 using your GitHub account
Received on Monday, 19 September 2016 23:46:19 UTC