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

Re: [pointerevents] Enable direct pen and touch to have different touch-action behavior

From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
Date: Fri, 05 May 2017 20:36:09 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-299569412-1494016567-sysbot+gh@w3.org>
I think <code>touch-action-pointers</code> is a cleaner solution.

I have different concern though: any of these ideas (<code>touch-action-pointers</code> or <code>pen-action</code>) adds another dimension to how pens behave, on top of [InputDeviceCapabilities.pointerMovementScrolls](https://wicg.github.io/InputDeviceCapabilities/#dom-inputdevicecapabilities-pointermovementscrolls). I have a feeling that one of them should be redundant when we already have <code>pointerType</code>.

For example, the outcome is not obvious when pen events have pointerMovementScrolls == false but the same events are supposed to <code>pan-y</code>. (This is true for pointerType="touch" even today, but perhaps nobody expects pointerMovementScrolls == false here.)

Am I the only one to find three levels of parameters (type + capabilities + action) too complicated? Any chance we may not need pointerMovementScrolls at all if we have touch-action-pointers?

GitHub Notification of comment by mustaqahmed
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/203#issuecomment-299569412 using your GitHub account
Received on Friday, 5 May 2017 20:36:15 UTC

This archive was generated by hypermail 2.3.1 : Friday, 5 May 2017 20:36:16 UTC