Re: [pointerevents] Should a captured pointer send boundary events by default?

Although that particular UI seems weird to me but I guess that's just 
me and I totally agree we should make it possible for a developer to 
implement that UI.
@teddink, let me ask you this question regarding the boundary events 
in the case of that button since I got a bit confused how much of it 
is automated. Do you expect the developers to change the style of the 
button based on pointerleave/enter as @patrickhlauke suggested?
How about this as an alternative solution? Correct me if I'm wrong 
here. If we remove the hit testing while a pointer is captured 
(meaning we don't send the boundary events) developers who want to 
implement that UI can still do an element boundary check of 
"pointermove" events with a much smaller cost I assume in this case or
 the worst case just using elementFromPoint which has the same 
performance hit in the worst case as us always doing the hit test. So 
basically what I'm saying is that this UI you have in mind is still 
very well possible even if we don't send boundary events and of course
 not in a very hard way as it's just a boundary check of the element. 
I guess counting the lines this will probably be the same as adding 
the handlers to pointerleave/enter and toggling the style.

-- 
GitHub Notification of comment by NavidZ
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/61#issuecomment-220212202 
using your GitHub account

Received on Thursday, 19 May 2016 02:28:53 UTC