The recent commit Merge branch 'lyonbot:pr' into pr merged code that utilizes the getCoalescedEvents() function for improved performance to PointerEvents. Unfortunately, this function is not supported on IOS or Safari as noted in the MDN Web Docs, so input appears to be currently broken on those devices. I have tested it on the iOS versions of Safari, Brave, and Firefox, and all experience the same issues. Attempting to use Weylus to send stylus or touch input does not result in any input other than the first contact, and results in errors being written to the webpage log, stating that e.getCoalescedEvents() is not a function and not defined. I do not have a MacOS device, so I cannot test its support, but I would assume its support to be broken when using Safari as well. I don't believe there currently is, but is there a way to disable usage of this function in this release? If not, is a way to disable this function that something that could be added (maybe even having the function be disabled as the default to guarantee it works out-of-the-box on most devices)? For now I'm just using the 2024.8.3 version which is working fine, but being able to use future versions would be lovely.
Hello,
The recent commit Merge branch 'lyonbot:pr' into pr merged code that utilizes the getCoalescedEvents() function for improved performance to PointerEvents. Unfortunately, this function is not supported on IOS or Safari as noted in the MDN Web Docs, so input appears to be currently broken on those devices. I have tested it on the iOS versions of Safari, Brave, and Firefox, and all experience the same issues. Attempting to use Weylus to send stylus or touch input does not result in any input other than the first contact, and results in errors being written to the webpage log, stating that e.getCoalescedEvents() is not a function and not defined. I do not have a MacOS device, so I cannot test its support, but I would assume its support to be broken when using Safari as well. I don't believe there currently is, but is there a way to disable usage of this function in this release? If not, is a way to disable this function that something that could be added (maybe even having the function be disabled as the default to guarantee it works out-of-the-box on most devices)? For now I'm just using the 2024.8.3 version which is working fine, but being able to use future versions would be lovely.
Thanks!