Voting starts in March for the Drupal Association Board election.
Hi guys. Very useful module - thanks.
The issue I've found only seems to occur on the iPad (i.e. no problem at all on the latest desktop versions of IE, Chrome & Firefox) but the issue is identical on both the Safari and Chrome browsers on the iPad2:
1. All my superfish parent menus (li... .menuparent) are not visible until one-touched (on the iPad, of course) whereupon the do become visible.*
2. Any childless superfish menu items (li... .sf-no-children) are not effected and remain visible (above the flexslider containers).
3. The superfish menus, all horizontal, worked fine before deploying flexslider.
4. I've only seen this error on the iPad(2) but its exactly the same in Chrome and Safari.
*I.E. the whole li element (with colors, a links and background image in the li element) is invisible - presumably trapped behind a z-index level somewhere - until the first touch whereupon the whole li element plus submenus appear as normal (on top of the flexslider containers).
I've searched and can see lots of threads on identical issues that affected these two modules together for IE7/8 browsers earlier this year, suggesting that it was a problem with missing z-index classes on FlexSlider, but I've found nothing specific to concerning the iPad/2.
Testing the same issue on the desktop version IE8 shows the li elements correctly positioned on top of the flexslider containers.
I appreciate this seems to look like a Superfish issue - except that the menus work fine without flexslider - where I was previously using the Views Slideshow option - before needing an adaptive solution.
I'll post the same issue on Superfish too - but I would love to hear from anyone with the same issue and what they did (precisely) to fix it. I presume it's all z-index related but everything I've tried so far doesn't seem to bring the un-touched li element over flexslider.
EDIT: cross referenced post is here: http://drupal.org/node/1704582#comment-6384746 but I'm still guessing this is likely to be a Flexslider issue (or same-name function? I'm only guessing).