- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 May 2020 07:41:01 +0000
- To: public-pointer-events@w3.org
@domenic from my perspective, what I'd like to achieve is: * we've crammed two different ways of describing a stylus/pen/pencil spatial orientation into the spec, because different authors will find either method easier/more aligned with what feels more natural to them (and it mirrors two different low-level APIs available on different platforms and the kinds of values they return) * we want to avoid forcing authors having to calculate both representations of a particular orientation they want when defining synthetic events - as the whole point was that authors can choose either the `tiltX`/`tiltY` or `altitudeAngle`/`azimuthAngle` way of looking at it because it's most natural/suitable/convenient to them in their app, it would then seem odd to require them to pre-calculate themselves what both representations are. The idea with the events is (based on the latests changes) that regardless of what the browsers get from the OS, they calculate the matching pair of values themselves. I'd like the same convenience (and speed) for synthetic events generated by authors somehow. -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/321#issuecomment-622286204 using your GitHub account
Received on Friday, 1 May 2020 07:41:03 UTC