- acactwAsked on October 01, 2015 at 06:40 AM
I tested the form on the destop, ipad and iphone.
It worked fine one these devices.
But when it came to android phone, specifically Asus Zendone 1,
the submit button malfunctioned.Also, the " I agree those terms" checkbox is invisible on the android phone as well.
Please help me to fix it.
- KadeJMAnswered on October 01, 2015 at 11:01 AM
I see that you appear to be having an issue with the submit button not working properly on your Android Device.
Are you using just the form link? Or is it embedded somewhere?
- rdobryAnswered on October 28, 2015 at 01:05 AM
I have the same problem.
With Your form from link above, and my own.
I try direct link and embedded js - no difference
Android 4.4.2 core 3.10.20 / chrome 33.0.1750.132 (I can not submit form)
When i upgrade chrome to version 46.0.2490.76 all working fine
Android 4.2.2 core 3.4.5 /chrome 40.0.2214.109 (working fine)
- JotForm UI DevelopermertAnswered on October 28, 2015 at 04:44 AM
If your forms are already mobile responsive, you can try to embed your form using İFrame method and make its height lower. Below, you will see the blue marked area to change the forms height and also, between the <iframe>...</iframe> part is the only part you need to copy.
<iframe id="JotFormIFrame" onload="window.parent.scrollTo(0,0)" allowtransparency="true" src="//www.jotform.me/form/51342932947460" frameborder="0" style="width:100%; height:600px; border:none;" scrolling="no"> </iframe>
I hope this one will help you. Please, let us know the updates.
- rdobryAnswered on October 28, 2015 at 01:54 PM
The problem does not lie in the amount of form just in the widget terms and conditions. When it is required do not submit form. Sometimes the text "terms and conditions" is visible sometimes not. Disabling requirements t & c lets you submit the form. The situation is likely takes place just on the original, not updated Chrome with Android 4.4
Sorry my english is not very well
- KadeJMAnswered on October 28, 2015 at 03:32 PM
We understand you are having the same issue as the original thread at first but I've moved your thread to this new thread here as a separate new issue even though it is related.