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
Sorry if this is the wrong place, but I spent hours yesterday digging into an issue. I am mostly reporting so others encountering this can feel a little more sane.. :)
Random Windows users were complaining that top level menu items were not clickable anymore. That is, they would not follow to their usual links, all they would do is open and close their submenus (or do nothing if they didn't have submenus).
After significant amounts of debugging, we found that they were all users with Windows devices with touchscreens (both laptops and desktops). "isTouch" was coming up as true on those devices and, for some reason, Chrome 47 is now triggering "ontouchstart" events even for mouse clicks. We believe this latter part is a bug in Chrome, but either way, it affects the accessible mega menu's operation when in "touch" mode.
Our workaround has been to hard code isTouch as false and now everything works fine, even on iOS and Android as both Safari and Chrome seem to be smart enough to deal with initial clicks representing hover states.
The text was updated successfully, but these errors were encountered:
It's been a while now so I can't remember, but I seem to recall I merely searched the code for isTouch and when it was checked, I forced it to be false.
Sorry if this is the wrong place, but I spent hours yesterday digging into an issue. I am mostly reporting so others encountering this can feel a little more sane.. :)
Random Windows users were complaining that top level menu items were not clickable anymore. That is, they would not follow to their usual links, all they would do is open and close their submenus (or do nothing if they didn't have submenus).
After significant amounts of debugging, we found that they were all users with Windows devices with touchscreens (both laptops and desktops). "isTouch" was coming up as true on those devices and, for some reason, Chrome 47 is now triggering "ontouchstart" events even for mouse clicks. We believe this latter part is a bug in Chrome, but either way, it affects the accessible mega menu's operation when in "touch" mode.
Our workaround has been to hard code isTouch as false and now everything works fine, even on iOS and Android as both Safari and Chrome seem to be smart enough to deal with initial clicks representing hover states.
The text was updated successfully, but these errors were encountered: