Re: Impact of pointer capture on hit testing requirements / performance

Forgot to add subject, prev. comment:
http://lists.w3.org/Archives/Public/public-pointer-events/2014AprJun/0022.html

Also I am a bit confused with this 'avoid pointerover/out handlers on the
element and all its ancestors'--why need to check ancestors for
pointerover/out events when pointer capture is active? In case with js
polyfill. this check might be slower than just hit test.

2) Pointer Events requires a hit test on every move, although it can be
> avoided if the developer is careful. Eg. they must call setPointerCapture
> AND avoid any pointerenter/leave handlers on the element with capture, and
> also avoid pointerover/out handlers on the element and all its ancestors.
> We are concerned that in practice developers will rarely be this careful.



-- 
@nekrtemplar <https://twitter.com/nekrtemplar>