Android issues with insert before about responsive-nav.js

[arielsalminen]

What browser are you using? Just tested on Galaxy S III, works without problems.

[rgfx]

I used the stock browser. I neglected to mention that the S III was an emulator as well on browserstack.com. So perhaps it does work. I have found the emulators to be reliable with testing.

[jeradg]

Just had this exact same problem on Browserstack with the S III. (Click on nav-toggle, menu appears for a half a second and closes immediately.) Works on all other devices tested.

Live site: http://jeradgallinger.ca/hosted/slf/tribunal/draft4/

Is this just a Browserstack problem?

[arielsalminen]

@jeradg Any idea what Android OS version Browserstack is using with S III?

[nfletton]

I can confirm this happens in the latest version of Google Chrome for the following physical devices:
Motorola Xoom Android 4.03
Nexus S Android 4.1.1

Latest Firefox version on these devices works fine.

I've switched back to insert: "after" and used CSS to get the positioning I want to achieve.

[arielsalminen]

@nfletton I’ll investigate this now!

[arielsalminen]

@nfletton Just tested on Galaxy S 3, Nexus S and Nexus 7 with both Chrome and the native webkit browser (if available) using the option insert: "before." Couldn’t reproduce the issue with few different test cases I tried.

Could you also confirm that this problem exists with the latest version released few days ago, 1.0.20? Easiest way is to go into this temporary directory I added under my site and open the index.html which uses insert: before option.

Demo here: http://viljamis.com/temp/index.html

[nfletton]

@viljamis Your demo had insert:after when I tried. However, I tried 1.0.20 (I was using 1.0.15) on my under construction site and I could no longer reproduce the problem.

Thank you.

[arielsalminen]

@nfletton Sorry about that, I was testing some stuff earlier and forgot that I pasted the link here too (now changed). Anyway: great to hear it’s working as I tried to fix this problem in the latest release. Hopefully this doesn’t happen anymore.

Closing the issue for now…

[jeradg]

Working fine for me now. Thanks.