What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.


  • Profile Image

    Shuffle widget is moving submit button to top

    Asked by Harshecube on October 07, 2016 at 04:51 AM
    Screenshot
    shuffle widget
  • Profile Image
    JotForm Support

    Answered by owen on October 07, 2016 at 05:30 AM

    Hi,

    You can simply drag a field and re-arrange its position. Please try it and check. If the issue still persists please get in touch with us.

    If you need further assistance let us know. 

  • Profile Image

    Answered by Harshecube on October 07, 2016 at 06:12 AM

    Hi ... 

    In my "Carlsberg" quiz , I have put Shuffle option (though Submit button field number is added as an exception for Shuffle so that it does not change position)

    Currently,Submit button is placed at end of form 

    However, when I am running the quiz on multiple tabs of browser ( this is required as many participants will attempt quiz) then Submit button position changes 

    How to rectify this?

  • Profile Image
    JotForm Support

    Answered by jonathan on October 07, 2016 at 10:44 AM

    I was able to reproduce the issue on my test form.

    You can try also my test form.

    test form: https://form.jotform.com/62803862899977

    I was able to fix it by setting the Shuffle widget configuration to this.

     

    Can you also try the same settings on your form. I assigned the Submit button field ID# in the excluded field.

    Let us know if this did not fix the issue.