Re: Can we change default radius to 0 in the touch events extensions

On 06/05/2014 09:13 AM, Rick Byers wrote:
> Secondly, using X and Y for the radius is somewhat limiting.  X11 and 
> Android instead use an ellipse model of touch contact with touchMajor, 
> touchMinor and touchRotationAngle.  I've just learned that the Nexus 
> 10 does a really good job of supporting this (you can see it by 
> enabling "show touch locations" in developer options).  I'm not aware 
> of any device that returns touch width/height so in practice chrome 
> always reports radiusX==radiusY.  So I'd prefer we change this to 
> radiusMajor, radiusMinor and rotationAngle properties.  OSes like 
> Windows 8 that report contact geometry in terms of width/height can 
> still be properly supported - rotationAngle would just always be 0, 
> but the inverse is not true.
Earlier versions of the v2 spec had a "rotationAngle" property that 
worked like this:

https://dvcs.w3.org/hg/webevents/raw-file/c8eccbb92b31/touchevents.html#widl-Touch-rotationAngle

It was removed (by accident?) when the document was changed from Touch 
Events v2 to Touch Events v1 Extensions.

Received on Thursday, 5 June 2014 16:33:46 UTC