- From: Sanket Bhuite via GitHub <noreply@w3.org>
- Date: Fri, 10 Apr 2026 19:38:46 +0000
- To: public-pointer-events@w3.org
Mandating a minimum dispatch frequency might improve precision, but it could also introduce performance and power concerns, especially on low-end devices and mobile platforms. Instead of enforcing a fixed minimum like 250Hz, it might be better to: * Allow browsers to dispatch at hardware rate when possible * Encourage use of `getCoalescedEvents()` for high-precision tracking * Possibly define a recommended (not mandatory) minimum A strict minimum frequency could unintentionally increase CPU usage even when applications don't need that level of precision. Adaptive dispatch based on hardware capability and event coalescing may provide better balance between precision and performance. This would preserve flexibility while still enabling high-frequency input for apps like drawing tools, games, and precision UI interactions. -- GitHub Notification of comment by sanketbhuite Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/621#issuecomment-4226308911 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 April 2026 19:38:47 UTC