- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 May 2016 18:57:12 +0000
- To: public-pointer-events@w3.org
> If this value is going to have future utility, the OS or browser should not fill in numbers if it really doesn't know. Let a width/height of 0 or undefined represent a missing or unsupported value. Software at the application level can recognize that and provide a default. So removing this, basically? > a default value should be provided by the user agent to approximate the geometry typical of that pointer type Incidentally, for Touch Events, I seem to recall that some browsers do the same "fake" estimation of `radiusX`/`radiusY` (and on some devices, use these values to fake `pressure` even on non-pressure-sensitive touchscreens). however, http://w3c.github.io/touch-events/#widl-Touch-radiusX seems more specific that UAs should simply report 0 here and not approximate anything. I could live with that - but if we do this, it should be done very soon before there's a critical mass of sites/apps that rely on the "faked" geometry values -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/65#issuecomment-219130669 using your GitHub account
Received on Friday, 13 May 2016 18:57:14 UTC