W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2016

RE: [pointerevents] Spec implies mice can't support pressure

From: Ted Dinklocker <Ted.Dinklocker@microsoft.com>
Date: Thu, 21 Jan 2016 04:27:07 +0000
To: Rick Byers via GitHub <sysbot+gh@w3.org>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Message-ID: <BL2PR03MB2289FA4D657D29B11A160DE8EC30@BL2PR03MB228.namprd03.prod.outlook.com>
Sounds reasonable to me.

Also seems like a good opportunity to discuss whether it makes sense to do some work around force touch as well? It is easy to imagine a broader world of touchpads that support pressure and haptic feedback with scenarios for force touch.

Thoughts?

-----Original Message-----
From: Rick Byers via GitHub [mailto:sysbot+gh@w3.org] 
Sent: Wednesday, January 20, 2016 6:52 PM
To: public-pointer-events@w3.org
Subject: [pointerevents] Spec implies mice can't support pressure

RByers has just created a new issue for
https://github.com/w3c/pointerevents:


== Spec implies mice can't support pressure == The spec says: 

> For hardware that does not support pressure, including but not
limited to mouse, the value must be 0.5 when in the active buttons state and 0 otherwise.

Which implies it's impossible for a mouse to support pressure.  Fouch touch touchpads on Mac OS are a real-world example that violates this,  and I think we should plumb force out to `PointerEvent.pressure` on Mac OS.

Can we just remove the "including but not limited to mouse"?  Or replace it with "(for example, most mice)"?

Please view or discuss this issue at
https://github.com/w3c/pointerevents/issues/30 using your GitHub account
Received on Thursday, 21 January 2016 04:27:38 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 21 January 2016 04:27:38 UTC