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

If we were to make all pointer events implicitly captured, what would 
we do about the compatibility mouse events?  Today mouse events are 
(almost) always delivered to the same node as the pointer events.  I 
think it would be problematic to break that.  But it would probably be
 a huge breaking change for the web if mouse events suddenly became 
implicitly captured.

Perhaps the only pragmatic way out of this mess is to say whether or 
not an input device implicitly captures is a property of that device, 
perhaps exposed explicitly on 
[InputDevice](https://github.com/rbyers/InputDevice).  That doesn't 
necessarily seem terrible to me, when the different really matters 
developers can always explicitly indicate their intent with the 
capture APIs.  I also don't think it's entirely unreasonable to say 
that direct manipulation input devices should be implicitly captured, 
while indirect ones may not be.

-- 
GitHub Notif of comment by RByers
See 
https://github.com/w3c/pointerevents/issues/8#issuecomment-129482010

Received on Monday, 10 August 2015 14:58:30 UTC