Feature Request: Read-Only or Disabled input field attribute

  • Profile Image
    xtechpl
    Asked on February 04, 2013 at 04:53 PM

    What is the reason for disabling custom javascript in html field? Why don't provide this feature on responsibility of form creator? I could add many features eg. field disabeling.

     

    PK

  • Profile Image
    Mike_T
    Answered on February 04, 2013 at 06:13 PM

    Thank you for contacting us.

    Unfortunately, allowing JavaScript can cause XSS (Cross-Site Scripting) problems on our site, so that we were forced to disable that option.

    Please note that you can still get your form source code and use it for custom development.

    If you need any further assistance, please let us know. We will be happy to help.

  • Profile Image
    xtechpl
    Answered on February 05, 2013 at 09:10 AM

    Embedding source code is problematic - it need to be updated when backoffice changes form design.

  • Profile Image
    Deygus
    Answered on February 05, 2013 at 09:44 AM

    As far as I know there are no known or scheduled plans to modify the design on our end for the time being due to the conflicts that can occur. Perhaps for now though, you could explain more about what you were trying to do originally in the html field with javascript and we might possibly be able to help find a workaround.

  • Profile Image
    xtechpl
    Answered on February 06, 2013 at 08:30 AM

    I would like to fill content with custom data, and this part of content should be read-only. I've been trying to do this with pre-populating input's but i cant disable them without accessing form html DOM.

  • Profile Image
    jonathan
    Answered on February 06, 2013 at 08:52 AM

    @xtechpl

    Hi, I understand that using the form's source code will require you to update also the embedded code everytime you update the form in the form builder. But this is the only means to inject your own custom javascript code into the form to have functionalities not built-in the form builder.

    However, this is only problematic if you still constantly update the form -- perhaps finalizing the form to certain extent to minimize updating it everytime, -- will lessen or eliminate this limitation.

    The custom javascript that you will add to disable certain form fields will not affect the design of the form (you can edit/update this custom javascript code anytime without affecting the base form source codes.)

    You may also want to review this thread that has similar requirements as yours.

    Please inform us should you have further inquiry.

    Thanks. 

  • Profile Image
    xtechpl
    Answered on February 06, 2013 at 09:32 AM

    So maybe you could provide disabled attribute in form builder? That's not to much work to do?

  • Profile Image
    jonathan
    Answered on February 06, 2013 at 09:55 AM

    Hi,

    Your suggestion have merit on it. I actually had checked for similar request for this already -- disable field or read-only field feature.

    Since I could not immediately find one, I created one myself using your post. I hope it gets the approval, and be included in the feature updates.

    You will be inform as soon us news on this feature is available from our dev team.

    Thanks.

  • Profile Image
    xtechpl
    Answered on February 06, 2013 at 10:20 AM

    Ok, thanks for your involvement. I'm looking forward for changes.

  • Profile Image
    NeilVicente
    Answered on February 11, 2013 at 01:21 PM

    @xtechpl

    We have added the read-only property option to the following fields:

    Email
    Full Name
    Number
    Password
    Phone
    Text Box
    Text Area

    To go about this, simply right click on the field that you want to set as "Read-only", click Properties and set the option value to "Yes".

    By the way, because setting a field to disabled will in effect "remove" the field from the form (meaning the value cannot be changed and cannot be saved to the server), we decided not to implement it (the disabled attribute), so as to not cause confusion amongst our users.

  • Profile Image
    xtechpl
    Answered on February 12, 2013 at 02:34 AM

    Thanks for the new feature - your're fast.

    What do you mean by "not to implement it" you didn't implemented saving value of disabled field?

    PS. i do not see this probperty yet - have you published changes?

  • Profile Image
    NeilVicente
    Answered on February 14, 2013 at 05:45 AM

    @xtechpl

    We have temporarily removed it because it resulted to a few problems with the form builder. We will have it reimplemented at a later date, when the code changes have been refined.

    What do you mean by "not to implement it" you didn't implemented saving value of disabled field?

    Actually, setting an input to use the disabled attrribute will effectively prevent the data from being submitted, so it is basically useless in JotForm's context.

    Our plan is to implement only the read-only function.

    By the way, we will inform you via this thread when it becomes available. Thanks!