Not possible to open some Form Collapses on Android phone

I'm not sure they are related but suddenly only the first form collapse will open on my mobile android phone it's been working fine for the last month

All my forms have the same problem only some of the collapse bars will open

I see that the same issue was reported here: http://www.jotform.com/answers/496166.

Please refer to the mentioned thread for any updates regarding this matter.
Thank you.

This problem is not confined to my form. I have created a simple collapse test form and on my Android using Firefox the collapse bars will not open if, like my test form they are hiding these widgets  Range Slider, Gift Register, Infinite list, Terms & Conditions

Thank you for the clarification about the issue. We will try to test this furthermore to see if we can figure out what is going on with it and get back to you about it.

Also can you please tell us what version of FireFox and Android you are using that is giving you this sort of problem?

I am using Android 5.0.1 Lollipop Firefox 34.0.1

This problem started right after this collapse bar fix http://www.jotform.com/answers/493946

There are a lot of Android users this is causing more problems than the original glitch

Thanks for providing that extra bit of information.

I've done some further investigating on this particular issue and it appears that I'm unable to replicate the issue at the moment since the collapses are working on my side in my tests. 

Can you please also tell us what type Android-based Device you're using as well? 

I apologize for not asking that added question beforehand.

No problem I appreciate your assistance, I am using a Nexus 5

It seems to work OK on chrome but not Firefox

Thanks for the inclusion of that. I tried testing it again from my end with a couple different methods but it's working here still. However, I believe that your report of the issue is probably more accurate since I know mobile devices can sometimes appear to have peculiar occurrences more often than not a lot of the time.

Let us try to dig into this a little deeper in conjunction with the other thread that had fixed this to see if we can figure out what happened. We'll update you as soon as more is known.