> | When pointer capture is set, pointerover, pointerout, pointerenter, > | and pointerleave events are only generated when crossing the > | boundary of the element that has capture as other elements can > | no longer be targeted by the pointer. This has the effect of > | suppressing these events on all other elements. > > And as I know that means that there still 'll be hit-testing after > setPointerCapture because browser needs to know when pointer > leaves/enters boundaries of captured element. This is not a full hit-testing, though. The major cost of hit-testing comes from the tunnelling from the viewport to the target element, here we are already at this element.Received on Wednesday, 20 August 2014 21:47:49 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:10 UTC