You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, this is on Google Chrome, on a Windows 10 touchscreen laptop (Dell Inspiron 3505), Google Chrome Version 105.0.5195.127 (Official Build) (64-bit)
Out of the box, everything worked perfect when manipulating with the mouse, but it didn't respond to touch.
Took a quick look in the code and putting an (... || true) in the below pictured if statement (ln 119) got me the functionality I was after but now the mouse is unresponsive. I'm not sure if there is a reason to make these mutually exclusive but for my purpose I want to be able to use both. So, I commented out the if structure and it works as I was hoping for!
I don't understand the ("ontouchstart" in document.documentElement) method, but it never returns true for me, while using "onclick" does... odd, but I can confirm that the touch listeners are working for me regardless of this test method.
Personally I would prefer the listeners to be able to be activated / deactivated with a parameter input, then it either works or it doesn't, but that's just me.
Best Regards!
-Matt
The text was updated successfully, but these errors were encountered:
Hello, and thank you for the great work!
First off, this is on Google Chrome, on a Windows 10 touchscreen laptop (Dell Inspiron 3505),
Google Chrome Version 105.0.5195.127 (Official Build) (64-bit)
Out of the box, everything worked perfect when manipulating with the mouse, but it didn't respond to touch.
Took a quick look in the code and putting an (... || true) in the below pictured if statement (ln 119) got me the functionality I was after but now the mouse is unresponsive. I'm not sure if there is a reason to make these mutually exclusive but for my purpose I want to be able to use both. So, I commented out the if structure and it works as I was hoping for!
I don't understand the ("ontouchstart" in document.documentElement) method, but it never returns true for me, while using "onclick" does... odd, but I can confirm that the touch listeners are working for me regardless of this test method.
Personally I would prefer the listeners to be able to be activated / deactivated with a parameter input, then it either works or it doesn't, but that's just me.
Best Regards!
-Matt
The text was updated successfully, but these errors were encountered: