Adding a field with a unique name that contains onScroll always changes the fields unique name to onScrollDISABLED

  • Erin
    Asked on March 16, 2017 at 7:02 AM

    One of the fields in my form is being glitchy - its Unique Name (which used to be cinnamonscroll) has somehow changed to cinnamonscrollDISABLEDDISABLEDDISABLED

    I can't see any way that it would have been disabled, or how to enable it again. I've tried changing the unique name back to what it should be, but each time I exit the form it reverts back to DISABLED...

    https://www.jotformpro.com/build/60964699252974

    Jotform Thread 1093239 Screenshot
  • David JotForm Support
    Replied on March 16, 2017 at 11:31 AM

    I am able to reproduce this in my own form.  I am not sure why the Cinnamon Scroll text is causing issues with the unique name but when I return to editing the form, the unique name does indeed change.

    Here is the unique name after setting up the field:

    Adding a field with a unique name that contains onScroll always changes the fields unique name to onScrollDISABLED Image 1 Screenshot 30

    And here is the name after returning to editing the form:

    Adding a field with a unique name that contains onScroll always changes the fields unique name to onScrollDISABLED Image 2 Screenshot 41

    This doesn't seem to have any impact on the fields functionality. 

    I am unable to reproduce this with any other set of text.  I will forward this to our developers to have a look.  We will let you know as soon as we have further information.

  • David JotForm Support
    Replied on March 16, 2017 at 11:46 AM

    I did a bit more digging and it seems onScroll may be protected and is triggering a filter.  Anything with onScroll like Coupon Scroll or simply On Scroll is causing the same thing to occur.  We will let you know as soon as we have a solution.

  • Rose
    Replied on January 12, 2018 at 9:05 AM

    We are terribly sorry for this inconvenience caused to you. 

    The problem regarding the Disabled text adding to the unique name of the field should be fixed now. Everything should be saved correctly after all. However, if you see the same  problem for any of the field, we strongly suggest you:

    1. Open question properties of that specific field.

    2. Go to advanced tab and click to Field Details.

    3. Delete Disabled tags from the Unique Name part.

    We thank you again for your understanding and cooperation with us.