This is a frustrating bug that can prevent a person from hitting the menu item they intended to. It happens if the user opens the touch menu, expands one of the items, and then attempts to expand a different item below the original. On the down press, the original expanded menu collapses, but the action isn't registered as a click until the finger is lifted and there is something else in that position. The original menu item shouldn't collapse until the whole click is finished.
This can be tested on a desktop with the device emulation features in Chrome developer tools. Without something like that the menu will use mouse hover instead of waiting for clicks so this behavior will not be seen.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | tb_megamenu-touch_menu_fix-2333759-1.patch | 870 bytes | jmuzz |
Comments
Comment #1
jmuzz commentedThis is a simple change that works for my case. I don't think it will work correctly for menus that have more than 2 levels.
Comment #2
LeeUDO commentedHello, after applying the patch mentioned above and the patch from https://www.drupal.org/node/2011042 i am still having the issue mentioned by the original poster.
This issue however only seems to effect Ipads and Iphones using iOS7, which is a pain.
For a working example of the issue, go to https://gb.udostreetdance.com on a ipad, the menu has 3 sub-levels events>event type> the event itself.
The first two levels work find, whoever as mention by post #1, the third level is the one causing issues.
Any help would be appreciated.
Thank you
Comment #3
cecrs commentedThis patch worked for me, would be great to get it into the module! (And thank you thank you jmuzz, this one had me tearing out my hair!)
Comment #4
quondam commentedIn order to implement this fix the provided patch would need to be re-rolled so that it applies cleanly to the current 7.x-1.0-rc3 branch.
Comment #5
rbrownellThanks for the report and for contributing to the TB Mega Menu issue queue.
Drupal 7 reached end of life on January 5, 2025 and is no longer supported going forward.
As part of wrapping up Drupal 7 support for this project, issues that do not include a code-based resolution (including issues where the only patch is out of date and requires a re-roll) are being closed as Outdated as part of this cleanup.
This closure reflects the end-of-life status of Drupal 7 and the absence of an up-to-date fix we can act on, not the validity of the issue itself.
If the issue applies to a currently supported version of Drupal, please open a new issue with updated details.
Thanks again to everyone who contributed during Drupal 7’s lifecycle.