Bug(s) with "useClick:true" 1.6.0

[Spuds]

Using the example page at http://users.tpg.com.au/j_birch/plugins/superfish/#

1. Chrome 25:

• Flush cache ;)
• Go directly to require click tab
• Select a menu item
  • Select one of the resulting menu items that has an additional menu (a 2nd level menu)
• Click outside of that menu ... they never close ... e.g. two levels of menu stay open on the screen

2. FF 19:

• Flush cache
• Go directly to require click tab
• Select a menu item
  • Select one of the resulting menu items that has an additional menu (a 2nd level menu)
• Works as expected
• Do it again and the 2nd level menu simply appears and disappears

[joeldbirch]

Thanks, I'll have a look at this.

[joeldbirch]

v1.6.2 fixes the Firefox bug.

It's not clear to me whether the first part of this issue is a bug. Obviously it would be preferrable for the behaviour to be consistent across browsers, but which is correct? Firefox or Chrome? If the feature is useClick, should not the submenus stay open until clicked, given that useClick currently applies to opening and closing the submenus? I bet there are good arguments both for and against.

[joeldbirch]

I'll close this issue as the main bug is fixed. Feel free to open a separate issue to discuss the "staying open" thing.

[joeldbirch]

My fix for the Firefox thing wasn't good. It blocked links with subs from being followed in Firefox! Have pushed an update to fix that, but this issue now needs a real fix, so it is being reopened.