Try this. Select click menu option in profile. Open a droppy.
Click somewhere outside the theme wrapper/frame divs (ie: body background).
Menu doesn't close. Just stays there. Click again inside theme wrapper > menu closes.
Had a quick look inside the jQ stuffz but couldn't see anything obvious. Should be tweaked so that clicking anywhere outside the menu closes it, IMO.
I've been using this on my homecooked click menu, which probably isn't directly usable with Superfish but illustrates the point.
// Click anywhere else to close.
$(document).live("click", function(e) {
var $clicked = $(e.target);
if (! $clicked.parents().is("li.dropmenu"))
$("li.dropmenu>ul").css("display","none");
});
ETA: Also, looking at Superfish, it's using some of the slowest jQ bits to deal with its eye candy (ie: show/hide instead of css("stuff")).
https://github.com/emanuele45/Dialogo/commit/97945aaf5f8bc1875c165d162b74528ac0a6c43d#commitcomment-3353881
Also, As of jQuery 1.7, the .live() method is deprecated. We are on 1.9.1
Fair nuff. Point was the trigger for closing seems to be restricted to areas within the theme wrapper, which seems like a buglet to me. It can just as easily be coded to close the menu if you click anywhere.
Totally agree ... Joel is aware of the issue, its mostly why the click stuff was separated from the hover stuff ... the click (or off click) acted very differently across multiple browsers, tablets, phones, os's Of course since he did that he has not done any work on the click side of things, I'm sure he will get back to it at some point, if someone else in github land does not do it first.
Uber bump, this is still a thing.
I know, it has not been moved to fixed. :P
Aye but it's been 3 years, time to look at it :-[ I don't want the board to end up like the 7 pages of crap there are on smf.
Each bug has a priority, this one is one of the lowest.
The fact that bugs accumulate it's absolutely normal and physiological in any projects (AFAIK it's a well documented pattern), nothing to worry about.
For anyone who's interested and didn't already know: the reason it was coded this way is because iShiz won't recognise clicky on the body tag. Only works on children of body. If you wanted to sort things so that clicky worked anywhere, you'd need an extra div in the markup that covered the whole screen, with the forum stuffz inside that.
Easy to do. Whether or not it's worth doing is personal preference. Me? I don't care either way.