Re: [pointerevents] add altitudeAngle/azimuthAngle (#316)

thinking about this some more (though admittedly i'm slowly out of my technical depth here), essentially the two models differ at a fundamental level, tied to the kinds of sensors (or the data provided in the low-level/OS-level APIs). the `tiltX`/`tiltY` model is richer since it captures states that are simply not available/detectable in the `altitudeAngle`/`azimuthAngle` model ... those where a stylus is still pointing one particular way but the user went "over" the perpendicular mark.

![photos showing the pen going beyond perpendicular](https://user-images.githubusercontent.com/895831/77911024-08fae300-7288-11ea-9c1b-400632dbd73f.jpg)

wondering if it's sufficient to address this in prose? aknowledge that going from the `tiltX`/`tiltY` to the `altitudeAngle`/`azimuthAngle` model is "lossy"? and that on platforms that (natively/in their low-level APIs) only support the latter, certain nuances (like the pen being over the perpendicular) won't be captured/capturable?

also yes, @grorg @graouts i'd be interested if there's an official `azimuthAngle` for when a stylus is perfectly perpendicular (where it could be anything really)? is there a default/fallback of zero?

-- 
GitHub Notification of comment by patrickhlauke
Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/316#issuecomment-605964257 using your GitHub account

Received on Monday, 30 March 2020 12:16:36 UTC