Ipad behaviour at Mega Menu

I can’t see the benefit of a copy in the child’s theme.
This was my approach, unfortunately it doesn’t work that way.

function add_megamenu_touch_fix(){
?>
<script>
(function($){	
	$('#avia-menu .menu-item-mega-parent .avia_mega_div a').on('touchstart', function () {
		setTimeout(function(){ 

			$(this).closest('.menu-item-mega-parent').find('>a').removeClass('open-mega-a');
			$(this).closest('.menu-item-mega-parent').css('overflow' , 'hidden');
			$(this).closest('.avia_mega_div').css({
				'opacity' : '0',
				'display': 'none',
			});
		}, 500);	
	});
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'add_megamenu_touch_fix');

It can’t be the first time that a touch-friendly Mega Div solution has been demanded.
A Mega Div with Anchor submenu items is not unusual, is it? So please find a solution on that issue

Thanks Ismael – does not work in this way.

this is my solution for now – but i thought it was a bit oversized.
But that works on my test page – see private Content:

function add_megamenu_touch_fix(){
?>
<script>
(function($){	
	var megaParent = $('.menu-item-mega-parent');
	megaParent.on('click touch', function() {
        megaParent.trigger('mouseenter');
		megaParent.find('>a').addClass('open-mega-a');
    });	
	$('.avia_mega_div a').on('click touch', function() {
		setTimeout(function(){  
			megaParent.trigger('mouseleave');
			megaParent.removeClass('current-menu-item');
			megaParent.find('>a').removeClass('open-mega-a');
		}, 900);
    });	
    $('.avia_mega_div').on('click touch', function(e) {
        e.stopPropagation();
    });
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'add_megamenu_touch_fix');

no – this line has to be present. ( tested on a real device – not on simulated ipad )
The chrome simulation is good for a quick check – but in the end you still have to test it on the real device.

if you have the call of new pages, everything is not necessary anyway, it is just only needed if you want to navigate to a sublevel anchor link.

Thanks – yes i changed the timing to 500ms.
but i think this should be an implemented default behavior – like on hamburger the content must be accessible after click.
A closing button could be an alternative but from usability point of view the touchend is more intuitive to use.

Can be closed – if you like