- From: Rick Byers <notifications@github.com>
- Date: Fri, 03 Jun 2016 05:52:50 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc:
- Message-ID: <w3c/uievents/issues/17/223570648@github.com>
There's a good [discussion](https://discourse.wicg.io/t/additional-use-cases-for-inputdevicecapabilities/1138/9?u=rickbyers) of the need for this on WICG, based around [this use case](https://github.com/Leaflet/Leaflet/issues/4538). Key question is: how should this API behave on continuous scrolling devices, and can we identify those devices reliably on all OSes? On Windows I think we'd just want `ticks` to accumulate for every `WHEEL_DELTA` amount of accumulated delta (see [MSDN](https://msdn.microsoft.com/en-us/library/windows/desktop/ms645617(v=vs.85).aspx)). But [our experience](https://bugs.chromium.org/p/chromium/issues/detail?id=545234) suggests we may not be able to provide an API (like MacOS's [hasPreciseScrollingDeltas](https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSEvent_Class/#//apple_ref/occ/instp/NSEvent/hasPreciseScrollingDeltas)) which reliably identifies the type of scrolling device on Windows. /cc @dtapuska @ymalik @teddink --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/17#issuecomment-223570648
Received on Friday, 3 June 2016 12:53:47 UTC