Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
I have a Acer Spin laptop (with touchscreen!) running W10
maxTouchpoints returns 10 in Chromium (Chrome/Edge) and 10 in Firefox
So when you check for a > 0 value, it disables the use of the mouse
You need to always attach mousemove, and touchmove when the device has a maxTouchpoints value.
Or just bluntly always attach a touchmove handler; it will be ignored on non capable devices?
oh that explains it... I wonder why the Acer Spin doesn't register the touchmove? Sounds like pointer events is the better way to go. I feel like I've seen one of these kind of touch sniffing scripts that specifically does something with an ms prefix. Will dig a bit deeper and probably write a little thing up about it :D
Having normally used a "mobile/non-mobile" sniffing script, never really ran into this before. I do seem to remember some QA people I work with talking about something similar with the surface pro.
Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
thats interesting @dannyengelman - works on osx chrome for me... what browser are you on? Thanks :D
hasTouch returns true on Chromium and FireFox Desktop browsers; and then the "touchmove" doesn't capture mouse movements.
thats weird - what operating system and device are you on?
Usually I use a library to detect true mobile... for the snippet I figured touch points was good enough - would be cool to know why it fails.
what do you get for
navigator.maxTouchPointsin the console?Thanks for your input on this @dannyengelman - I'm curious to know whats going on :D
I have a Acer Spin laptop (with touchscreen!) running W10
maxTouchpoints returns 10 in Chromium (Chrome/Edge) and 10 in Firefox
So when you check for a > 0 value, it disables the use of the mouse
You need to always attach
mousemove, andtouchmovewhen the device has a maxTouchpoints value.Or just bluntly always attach a
touchmovehandler; it will be ignored on non capable devices?oh that explains it... I wonder why the Acer Spin doesn't register the touchmove? Sounds like pointer events is the better way to go. I feel like I've seen one of these kind of touch sniffing scripts that specifically does something with an
msprefix. Will dig a bit deeper and probably write a little thing up about it :DHaving normally used a "mobile/non-mobile" sniffing script, never really ran into this before. I do seem to remember some QA people I work with talking about something similar with the surface pro.
Thanks again for your help :D
It does do the
touchmove. Your code needs to (always) attach amousemoveEvent.oh i see what you mean :D