The "Submit" button disappears when a user misses our a required field.

  • Profile Image
    bakingfresh
    Asked on September 21, 2015 at 02:09 PM

    Hello,

     

    When a user completes my form and misses out a required field, or enters an invaild card number, (but does not know as this stage) then when the user clicks "submit" (in this case the 'submit button is entitled 'checkout'.) the user us reminded that they have either missed out a required field and/or they have entered a incorrec card number, but when this happens, the "submit" disappears from the form!

     

    I have extended the lenght of my form on my website, currently is set a 3000px in height, I have extended in too 4000px in height, however this did not fix the issue.

     

    Kind Regards

    Stephen

  • Profile Image
    Ben
    Answered on September 21, 2015 at 05:51 PM

    I took a look at your form and I ca not recreate the same. I immediately went to Checkout button and clicked on it, but as the errors were shown, this did not move the submit button a lot for me.

    I presume that you do not have the same error happening for you when you go to your form directly (the link that you have shared with us: http://form.jotformeu.com/form/52233614679358)

    If that is true, please do share the link to the page on your website where the form is embedded on so that we can check it out and see what is going on and to help you resolve this :)

  • Profile Image
    Bakingfresh
    Answered on September 21, 2015 at 06:07 PM

    Hello,

    i forgot to mention this is only happening when viewing the form on a mobile.

    On the PC it works fine. (Unsure on tablets)

     

    this is the link too the form

    http://bakingfresh.co.uk/pear%2c-almond---rosemary-tart.html

    if you view it on mobile, and click on 'checkout' with out filling in any details you'll see what I mean.

    regards

    stephen

  • Profile Image
    Charlie
    Answered on September 22, 2015 at 02:06 AM

    Hi,

    I tried your website link and this is how it looks like:

     

    I'm viewing it on an Android 4.4 device using Chrome browser.

    I assume you are already using the iFrame embed code? Did you previously used the default embed script code? If the problem persists, could you kindly share us a screenshot of the problem? And may we know what mobile device the error shows?

    We'll wait for your response.

  • Profile Image
    bakingfresh
    Answered on September 22, 2015 at 04:37 AM

    Hi, here's what I see on a IPhone  after clicking on checkout

     

  • Profile Image
    Mike_G
    Answered on September 22, 2015 at 01:01 PM

    I would like to apologize for the inconvenience. We were able to reproduce and saw the issue you're having. We are still working on a feasible solution for your issue and we will get back to you as soon as we find any solution and update you on this thread. Thank you so much for your patience. 

  • Profile Image
    KadeJM
    Answered on September 24, 2015 at 09:44 AM

    Thank you kindly for your patience with this issue and we do apologize about the delay.

    We were working on a possible fix for the problem but have noticed that you've managed to find a way around the problem on your end using a pagebreak field since I we don't recall that being there before.

    When testing this on my iPhone 6 in iOS 9 I found this issue happened due to the use required fields which when submitted as empty displayed a form warning that would push the submit button off your page into overflow and the use of your secondary forms in the embed iframe widget on the parent form only added to this problem.

    The best way to fix this entire problem would be to use injected css to just hide the form warning message as well as shrinking your field question spacing

    .form-error-message {display: none;}

    However if you are happy with just using the pagebreak instead then that is certainly okay too if you wish and you may certainly disregard if it is working good for you as of now.

    If you are still unable with this though then please let us know and I will gladly provide you with the current workaround I have come up with to try to resolve the issue better for you.