Touch interaction on Android isn't working about superfish

[joeldbirch]

Thanks for the report. It works on all of those browsers on my Nexus 7 running Android 4.2.2 when hoverIntent is enabled. I wonder what is different about either your device or the test page you are viewing?

[jtmohr]

I'm running Android 4.1.2.

Looks like the main difference between the examples and my menu is my top level links are relative urls and not anchor urls like in the examples.

I'll take a closer look and see if I did something else that may affect it.

[jtmohr]

I stripped my menu down to bare bones and it is still behaving the same for me.

The only difference that I can see is my menu has relative urls that lead to pages that exist.

The example menus do appear to work for me, but the top level links don't lead anywhere.

[joeldbirch]

Can I see the test page you are using, please? Need to eliminate any uncertainty about how it is set up and which files you are using, etc.

[joeldbirch]

I can confirm that if you don't use hoverIntent the list of non-working Android browsers matches your list exactly. If you do include hoverIntent all of the browsers mentioned work fine. There is a similar issue with Windows 8 IE10 touch interactions (although with a completely different event system, of course). I'll address these issues in the 1.6.x versions, after I release 1.6.0. There are lots of nice things in 1.6.0 that I don't want to hold up releasing any longer.

For now, for the best browser support just include hoverIntent (I strongly recommend it anyway).

I'll leave this issue open until it is fully solved.

[jtmohr]

I believe I found my problem:

I had the speed option set to zero:
speed: 0

I changed it to fast:
speed: 'fast'

And, it is now working for all browsers with hoverintent.

I thought it should be possible to put in specific numbers vs. 'slow', 'normal', 'fast'.

Thanks for the time you put into this issue.

[joeldbirch]

You can use a number. For example:

speed: 200

...which would make the delay 200 milliseconds. I guess if the delay is too low you get the same bug that happens when hoverIntent is not included (something I hope to address).

Glad you are seeing it working with hoverIntent.

[joeldbirch]

Rolling this issue into #46.