With "Hide when collapse" de-activated, you have to click the parent item before it becomes visible and click it twice to see the parent item itself. With "Hide when collapse" active, no submenu will ever appear, so the parent clicking behaviour should change accordingly that a single click is sufficient. I consider it unexpected and therefore buggy behaviour when a user has to click twice even with absent sub-menu.

I think this can be fixed by patching the tb-megamenu-touch.js but up to now I did not came up with a solution. Any hit or help is appreciated.

CommentFileSizeAuthor
#1 SingleClickHideWhenCollapse-2279103-1.patch2.01 KBñull

Comments

ñull’s picture

ñull commented
StatusFileSize
new SingleClickHideWhenCollapse-2279103-1.patch2.01 KB

The patch is an improvement. Still when the submenu items are displayed in the menu, then still the parent item needs a double click. What it is doing is allowing the default behaviour (click is link) when the sub-menu is open but hidden.

lubwn’s picture

lubwn commented

I am having the same problem. I solved it on frontend with following code. Since my menu has no submenus when on mobile, I just needed to redirect users on single click.

		// na single click tb megamenu open
		$('#block-tb-megamenu-main-menu div div ul li a').click(function(){
	  		var link = $(this).attr("href");
			window.location.href = link;
		});
rbrownell’s picture

rbrownell
he/him
Primary language English
Location Gatineau, Québec, Canada
commented
Status: Active » Closed (outdated)

Thanks 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.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.