News for hackers. Stuff that matters.
Re:Intent to Implement: Pointer Events in Chrome by gtjrossi on Wednesday March 25, 2015 @03:40PM (#9265406)
I can see value in finding a way to expose individual touch points from their new touchpad to JavaScript. We looked at doing something similar in IE, actually, but didn't get around to it in time.

If they want to do that, then they're going to have lots of compatibility problems doing it with Touch Events. Too much code out there expects the presence of Touch Events to mean a touch-only device. So if you enable TE on a laptop, suddenly sites stop working for mouse/track. :-( Pointer Events don't have this problem.

Re:Intent to Implement: Pointer Events in Chrome by camhenlin on Wednesday March 25, 2015 @03:44PM (#9265428)
Interesting thought, I'm not sure if PointerEvents would be handled correctly with a trackpad that would have traditionally used as Mouse input either. Seems like the developer would have to know how the trackpad is being used more than anything else since mouse/touch are very different behaviors.
Re:Intent to Implement: Pointer Events in Chrome by gtjrossi on Wednesday March 25, 2015 @04:03PM (#9265543)
yep, we imagined this would be surfaced as a new event.pointerType value, allowing code to specifically target the device if desired.