- From: Ziad El Khoury Hanna <notifications@github.com>
- Date: Fri, 22 Mar 2024 04:45:34 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 22 March 2024 11:45:39 UTC
I would like to also add that on macOS the scroll direction can be flipped (natural vs normal) which renders scroll-based interactions that don't scroll content (as @trusktr mentioned) inconsistent unless the scroll event includes this information (if the direction is flipped). Not to mention macOS's inertial scrolling. For context, I'm a developer of an online data visualizer for exploring satellite data on a map (the [Ocean Virtual Lab](https://ovl.oceandatalab.com) is an example). The scroll interaction is used in multiple components: * to zoom the map in/out (changes in steps, not continuously) * to change the transparency of a layer (changes continuously) * to change the current time (changes continuously) * to change the value of `<input type=range>`-like inputs (changes in steps, or continuously) And I have yet to find a way to iron-out the inconsistencies in scroll events between different browser and platforms 😔 PS: I apologize if these problems are out-of-scope for this issue, I just don't know where else to go -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/181#issuecomment-2014910091 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/181/2014910091@github.com>
Received on Friday, 22 March 2024 11:45:39 UTC