Spinner Field: shows up as a Text field in live mode.

  • TFMcDow
    Asked on August 25, 2017 at 11:00 AM

    I set up conditional logic based on a number chosen from a spinner, but now the spinner is not working. I do not want to replace it with a new form element or else I will have to set up my conditions again. Can you please help me?

    Jotform Thread 1232548 Screenshot
  • David JotForm Support Manager
    Replied on August 25, 2017 at 12:20 PM

    We will be glad to assist you. Please note that when you create a condition to show a field, there is no need to create a second condition to hide it, because that field will remain hidden unless the first condition is met, so you may delete these conditions:

    Spinner Field: shows up as a Text field in live mode Screenshot 50

    So, the best thing to do is to delete all conditions, and start fresh. So you can create conditions like this:

    Spinner Field: shows up as a Text field in live mode Screenshot 61

    Now, there is  a problem with the Spinner field, which shows up as if it were a text field:

    Edit mode:

    Spinner Field: shows up as a Text field in live mode Screenshot 72

    Live mode:

    Spinner Field: shows up as a Text field in live mode Screenshot 83

    I have tried clearing my forms cache, deleting that spinner field and adding a new one in my clone version, but the issue stills happens.

    I have reported this issue to our back-end team. You will be notified via this thread when it get fixed.

  • TFMcDow
    Replied on August 28, 2017 at 9:33 AM

    Great, thank you for all your help. I look forward to hearing back. 

    Erin

  • TFMcDow
    Replied on August 29, 2017 at 6:02 PM

    Out of curiosity, any estimate on how long this may take to fix? Sorry to be pesky. 

  • David JotForm Support Manager
    Replied on August 29, 2017 at 7:14 PM

    I see this issue has been assigned to one of our developers already. Unfortunately, there isn't an estimated time-frame for a resolution.

  • NeilVicente
    Replied on September 4, 2017 at 6:31 PM

    This is fixed now.

    Cheers!