Open JoeGermuska opened 9 years ago
right, it's either/or. We'd need a surface to explore this issue.
setting to future
milestone since I don't know when we'll get a surface for testing and development.
"Swipe to Navigate" also appears on Edge browsers, as verified using Remote IE. The Remote IE was horribly slow, so I am not sure I had a good test, but the "Swipe to navigate" was clear.
A zendesk user reported that after clearing the "swipe" message, navigation didn't work. If this affects all Edge users, this is a higher priority bug.
See also relevant conversation #457
It's not unique to the Surface. I have a regular Dell laptop with a touchscreen and have the problem there.
As a rough temporary workaround, I changed line 62 of TL.Browser.js to touch : false
as I don't need to support touch devices at the moment.
This also confused me for a while when testing with users. There seems to be quite a few laptops now that have touch screen capabilities. I wonder how many users actually use the touch screen feature? Most business users I've observed with these type of laptops still use them in the traditional way (with the trackpad, with a docking station, external mouse and monitor etc.) and never actually touch the screen.
Some kind of hybrid approach so it works for both mouse and touch devices would be ideal. I was just looking at the Hammer.js library for touch gestures and they seem to support both:
A Zendesk user reported problems using Chrome and Firefox on a Microsoft Surface device:
I don't have access to a Surface or other Windows device that supports both mouse and touch, but I would not be surprised if Timeline assumes
touch == !mouse