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

Re: [pointerevents] Extend pointer events to support raw trackpad data

From: Rick Byers via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 Dec 2017 03:07:18 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-350159887-1512702437-sysbot+gh@w3.org>
Note Edge is [shipping something kinda like this](https://blogs.windows.com/msedgedev/2017/12/07/better-precision-touchpad-experience-ptp-pointer-events/) where touchpad emulates a touchscreen, but without any of the API / spec changes we've discussed years ago.  @dtapuska and I expressed our reservations about this plan to @scottlow at TPAC.  Chrome has no intention of following this approach.

Chrome gets the same perf benefit with passive wheel listeners (sadly opt-in) and soon nearly the same by default with [async wheel events](https://github.com/w3c/uievents/issues/170). Although we'd probably have to define a 'wheel-action' CSS property to handle all the same edge cases with full fidelity.

We don't believe we could stop firing wheel events completely for touchpad scrolling for web compat reasons.  We know the vast majority of websites still don't support pointer events for touchscreen operations like panning. Also it could be confusing to emulate a touchscreen on devices with a touchpad but no touchscreen (MacBook, some Chromebooks).

All that said, I don't anticipate too much Interop pain from developers being surprised by the difference between Edge and Chrome here. I guess we'll see.
 

-- 
GitHub Notification of comment by RByers
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/206#issuecomment-350159887 using your GitHub account
Received on Friday, 8 December 2017 03:07:21 UTC

This archive was generated by hypermail 2.3.1 : Friday, 8 December 2017 03:07:21 UTC