- From: Dave Methvin via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 May 2016 18:05:00 +0000
- To: public-pointer-events@w3.org
It seems like 26 is a somewhat bogus answer that isn't dependent on the actual width of pointer contact. I get 26 on my Lenovo X1 Carbon in Edge and 21 in IE11, regardless of the fatness of the finger I use. :smile: Also, if the screen is zoomed by a double-tap the value becomes a constant 14 on both browsers. :question: http://jsbin.com/fefise/edit?html,js,console,output 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. (How would hovering touch devices be handled anyway? Seems like you'd want some sort of opt-in at `addEventListener` time and an elevation value on events?) For mouse cursors, on Windows at least a cursor editor makes you define a hot spot (generally the top left) and the rest of the cursor takes up space on the screen but is not part of the hot spot. So it would seem for that case you could validly define the width/height of the pointer to be 1x1? -- GitHub Notification of comment by dmethvin Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/65#issuecomment-219117075 using your GitHub account
Received on Friday, 13 May 2016 18:05:02 UTC