Re: TouchEvent sub-pixel precision

I think we should use this change as the first test of our TouchEvents
errata process.  It's a simple and non-controversial change, so it's mostly
mechanics.  We just need to replace each "long" for pageX/Y clientX/Y
screenX/Y values in the spec to "double".  What can I do to help make that
happen ASAP?


On Wed, Dec 18, 2013 at 1:09 PM, Scott González <>wrote:

> I agree that Mouse and Touch should have the same precision.
> On Tue, Dec 17, 2013 at 7:11 PM, Rick Byers <> wrote:
>> Hi,
>> The latest CSSOM View editors draft proposes a modification to MouseEvent
>> (and others) to enable fractional co-ordinates:
>>  This is most valuable in high-dpi scenarios (i.e. essentially all
>> tablets/phones and now many laptops) to provide more precise co-ordinates
>> to applications, so that they can result in maximum smoothness for slowly
>> moving elements.
>> I've suggested (
>> that if they're going to modify MouseEvent for this, they should modify
>> Touch at the same time.  Without this, for example, it's impossible to
>> implement scrolling in JavaScript that is as smooth as browser native
>> scrolling.  I don't think there's any good reason for Touch to be 2nd class
>> to mouse in this regard.
>> Thoughts?
>>   Rick

Received on Friday, 16 May 2014 16:53:51 UTC