W3C home > Mailing lists > Public > public-pointer-events@w3.org > October to December 2017

Re: [pointerevents] What should be the width/height of touch pointerUp?

From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
Date: Thu, 02 Nov 2017 20:48:05 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-341553274-1509655684-sysbot+gh@w3.org>
@mingchou to my understanding yes. But more accurately we report what the device reports us. So the device is in charge of translating that geometry to a number. If it can report a valid width and height for a hovering pointer we should be using that.

@mustaqahmed I believe the decision for the width/height=1 for mouse was that if we had a device that doesn't support reporting the width/height we set it to undefined and since the undefined value was problematic for the existing web we decided to call the undefined the value 1 (which could also be a real value reported by the device).
Following the same reasoning we can just set the pointerup for touch (or any other pointer) to 1 if we didn't get any valid width/height from underlying API. Does that sound reasonable?
Then if a device wants to define a default value or have the capability of calculating the width/height for the hovering touch (or any other pointer) they can just report that number and will use that.

-- 
GitHub Notification of comment by NavidZ
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/225#issuecomment-341553274 using your GitHub account
Received on Thursday, 2 November 2017 20:48:06 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 2 November 2017 20:48:07 UTC