Re: [uievents] Expose 'direction-inversion' in wheel events (#57)

@jacobrossi: I agree that inconsistency across devices isn't great, but I'd argue that inconsistency within a single device is even worse (think: a single person experiencing different behavior between a native app vs. the web). And the vast majority of users are going to be feeling inconsistencies of that sort. There are already plenty of cross-platform inconsistencies that are considered "good" since they embrace native conventions (e.g. differences in text rasterization).

An example close to my heart, try http://onshape.com/ on a Mac without a mouse. 3D navigation is currently extremely unergonomic. While they can (and plan to) improve click-less trackpad orbit/pan support, it will be impossible for them to do so in a way that would be on-par with native CAD apps on the platform (say, where 3D orbit gestures were mapped to the direction of a user's fingers).

(See https://forum.onshape.com/discussion/comment/12119 )

@RByers: putting the data on InputDeviceCapabilities makes a ton of sense.


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/57#issuecomment-171520190