Re: [pointerevents] Pointermove should not require a hit-test by default

> maybe philosophical, but is a stylus still a direct manipulation 
input when it's hovering (which still fires certain events, on 
supported devices)? because at that stage, your movements in the air 
are indirectly moving a separate cursor drawn on the screen...
> perhaps it should only implicitly capture once it makes contact with
 the surface, and require explicit capture otherwise? or is that 
getting too granular/magic?

Oh yeah I've always expected "implicit capture" to take effect on 
contact only.  Personally I wish we had separate events for hover-move
 and drag-move, but it seems fine to me for hover-move to be  
never-captured pointermove (as spec'd today) and drag-move to be 
implicitly-captured (but explicitly re/un-capturable) pointermove.

GitHub Notif of comment by RByers

Received on Monday, 10 August 2015 16:43:05 UTC