Doesn't work with iPad

I know this is only a few days old since last post but it does sem that lack of Touch device support is going to be an issue on a site I am currently working on. I mean iPhone has been out for a while now. Does anyone know what timescale for this issue to be addressed?

There are a few other sites that suport mega-menus that seem to provide better support for touch devices that might be of some interest:

http://www.concrete5.org/marketplace/addons/mega-menu/
http://johnlewis.com

Not sure this is the right place to post but I could not find any examples of GigaMenu to see it working on touch devices and ie6. Do you have a link to the site you worked on?

Gigamenu does seem to work though?!

Best solution for me based on #10 (thanks) was to add:

	// Remove href from menu parent items for mobile users
	$(".megamenu-menu").bind('touchstart', function(e){
		$('#megamenu-primary-links h2.megamenu-parent-title a').removeAttr('href');
	});

I've included this in megamenu.js around line 170.

Simply removing the href (link) allows the menu to activate. I'm not sure if this takes care of the mouseout (closing the menu), although I'm not too worried about this for mobile users (the menu fills most of the screen on an iphone).

For 7.x-2.x

What is the ideal UX for this? Hover is more convenient on PCs. The top level items have to be clickable in most cases, and touch users will also have to click to activate.

Some options are:

• Arrow icon or other clickable "Drop" activator -- maybe hover still works for PC's but touch users can also click the icon
• Double clicking (this seems like bad UI, unless there is some additional indicator)
• Listening for different device types (might require frequent updating)
• Listening for Hover before click vs click only (not sure if this works)

Modifying #10, I included the following in megamenu.js. This should fix the scope, while allowing for parent items with no drop down to go to their respective pages:

// Remove href from menu parent items.
function megamenu_open_progress() {
if ($(this).find('ul.megamenu-bin').get(0)) {
$(this).find('h2 a').removeAttr('href');
//alert('anchor removed');
}
}

//Display dropdown
$("#megamenu-main-menu h2.megamenu-parent-title a").bind('touchstart', function(e){
if($('#megamenu-main-menu li').find('.megamenu-active')) {
$('.megamenu-parent').bind('megamenu_open', megamenu_open_progress);
$('.megamenu-parent-title').bind('touchstart', megamenu_open);
//alert('this is visible!');
} else {
$("body").bind('click', megamenu_closeAll);
$('.megamenu-parent').bind('megamenu_close', megamenu_close_progress);
//alert('this is hidden!');
}
});

// Add mobile-friendly off trigger.
$('html').bind('touchstart', function(e){
megamenu_closeAll();
oldParentIdx = -1;
});

$(".megamenu-menu").bind('touchstart', function(e){
e.stopPropagation();
});

I also need to make the site I'm building with Megamenu work on iPad, but my team has decided that rather than attempting to support two slightly different behaviors (hover-to-expand on desktop and click-to-expand on iPad), we'd rather just get rid of the hover functionality entirely. Thus I'm currently working on a fork of 7.x-1.x (because I can't seem to find any actual code in the 7.x-2.x branch of the git repo) which takes out the expand-on-hover functionality, replacing it with expand-and-stay-open-on-click, which I'm calling "sticky menus."

I'm posting here for two reasons:
1. Would this "sticky menus" functionality make sense (or be doable at all) as an optional mode for Megamenu?
2. Do you folks, who are much more familiar with the code than myself, have any suggestions on how best to implement this?

I'm almost done with my patch that will enable Sticky Menus (plus several other improvements like AJAX forms in the "configure mega" pages), but I've got a bit of a conundrum. My code depends on the patch submitted in #1598510: Import/Export settings (Features integration), and also includes the change I made for #1617072: Individual "configure mega" pages behave strangely. So it seems like applying a patch based on my changes would be really sketchy.

What does one do in this situation? I've never done significant work like this on a contrib module before.

coredumperror: post your patch file. Someone can always go through and select the parts they want - it doesn't ALL have to be used.

Alternatively, post a number of patch files which do one specific thing, rather than one patch file which achieves a number of things.

In the 2 months since I posted my original intent to make a patch, I've made numerous additional alterations and improvements to Magamenu. Unfortunately, I've also completely lost track of which changes are mine and which are based on other patches that I applied. So, the attached patch is based on the 7.x-1.x branch, and it incorporates all of the differences between my currently-in-use Megamenu code, and that branch's last commit (in March).

I also make no promises that the upgrade code is perfect. I tried my best to make it look right, but I've never written upgrade scripts before, and I dont know how to test it.

Wow - there's a lot going on in there, that's for sure. I am going to run through it at some stage and pull out the bits I'm after. I will break it into a few smaller patches then.

Sorry it's so complicated! I'm not at all an expert in patching, or git in general, for that matter, so I have no idea how to break a patch up into different functionality changes. And I did make several significant, wide-ranging changes across pretty much the entire Megamenu code base, many of which were stylistic/best-practices changes.

Just wondering where Megamenu is right now in terms of 'touch' suitability. I see that there is a recent Dev release and wondered whether second touch (mouseout) behaviour is now provided.

cleaner text.

The Modernizr javascript library can provide a lightweight means of detecting whether a device is a Touch device. This patch assumes that you have loaded the Modernizr library with a build configured for the "Misc: Touch Events" option.

The attached patch detects whether the modernizr library is included, and if the device is a Touch device, the menu triggering behavior is adjusted.

#22 works quite well, but unfortunately it now seems to be impossible to select the root items actually on the main menu bar. Clicking on one of these items opens up the mega-menu ok, clicking on it again closes the mega menu. How can I get it to actually select the item on the bar? The only choice seems to be to hold the item selected and wait for the 'open in a new window' option to pop up.
(This is on an iPad)

We would need some other way of doing this. Third library with device detection seems overkill.