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

[pointerevents] Should spec mention OS/UA features like palm rejection?

From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
Date: Fri, 23 Dec 2016 13:35:08 +0000
To: public-pointer-events@w3.org
Message-ID: <issues.opened-197370341-1482500107-sysbot+gh@w3.org>
patrickhlauke has just created a new issue for 
https://github.com/w3c/pointerevents:

== Should spec mention OS/UA features like palm rejection? ==
Looking over https://w3c.github.io/pointerevents/#the-primary-pointer 
(in relation to 
https://github.com/w3c/pointerevents/issues/164#issuecomment-268988711)
 we have information such as 

> Only a primary pointer will produce compatibility mouse events. In 
the case where there are multiple primary pointers, these pointers 
will all produce compatibility mouse events.

and

> NOTE
> When two or more pointer device types are being used concurrently, 
multiple pointers (one for each pointerType) are considered primary. 
For example, a touch contact and a mouse cursor moved simultaneously 
will produce pointers that are both considered primary.

One thing the spec doesn't mention is that some OS/UAs may have 
additional built-in features like palm rejection (where once you use a
 pen/stylus, touches are ignored) or similar (e.g. on Surface 3, while
 you're actively touching/using the touchscreen or stylus, the 
trackpad on the keyboard is disabled, meaning you can't have a 
touch/pen and mouse at the same time - although once you plug in an 
external usb mouse, that does work).

I'm thinking some form of non-normative note here in that section, 
just so that this doesn't come as a surprise to developers?

Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/165 using your GitHub 
account
Received on Friday, 23 December 2016 13:35:09 UTC

This archive was generated by hypermail 2.3.1 : Friday, 23 December 2016 13:35:09 UTC