Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox

  • asccombaillaux
    Asked on November 27, 2014 at 5:58 PM
    Than how can I force user to navigate through the end of the conditions before allowing him to tick the box "agree with terms and conditions"
  • asccombaillaux
    Replied on November 27, 2014 at 6:33 PM

    Hi,

    I tried to apply your proposed solution to the widget but it doesn't seem to work, beside the fact that I think that an "Iframe" instrctuon only insert a page within a page not adressing my popup window requirement or I probably misunderstood your point. If tht's the case sorry for my thickness.

    Regards,

    Georges

  • Charlie
    Replied on November 27, 2014 at 6:37 PM

    Hi,

    Unfortunately, this is not possible if you are using the widgets, as they have a specific settings. I do have in mind a possible workaround but will need to incorporate a custom javascript/jquery code inside the source code of the form, you will then need to embed the form's source code to your website for it to work.

    If you would like to try it, please do send me the form's URL so that I can take a closer look.

    Thank you.

  • asccombaillaux
    Replied on November 27, 2014 at 6:39 PM

    Hi,

    Here is the utl: http://form.jotformeu.com/form/43016419622348

    Thanks for your help

    Georges

  • Charlie
    Replied on November 27, 2014 at 10:01 PM

    Hi Georges,

    I tried a couple of things using a custom javascript to disable the Terms widget and force user to scroll first before they are able to proceed. But unfortunately, I can't make it work, I believe this is because we can't pass javascripts to the widgets server. I'm currently doing a workaround using the custom fields and editing in manually in the source code. I'll post it here if I'm able to make it work.

    For the meantime, there's no other way to make the user aware that he/she needs to read or scroll the terms before proceeding.

    Regards

  • asccombaillaux
    Replied on November 28, 2014 at 5:59 AM

    Hi Charlie,

    You came to the same conclusions as I tried to use custom javascripit my mimicking the form popup integration schema wihtout succes.

    I'l use your suggested solution.

    Thanks for you help and time, I do appreciate all the jotfomr support tema for there responsivness and expertise.

    Best regards,

    Georges

  • Charlie
    Replied on November 28, 2014 at 8:48 AM

    Hi Georges,

    Thank you for the compliments. Here is the workaround that I have, you will need the source code and edit from there and embed it to your website. But, I will still escalate your request as a feature request, so that our developers can take a look at it and see if they can implement it directly to the widgets. 

    Here is the guide for the workaround that I thought.

    1. Instead of widgets, I used the default checkbox and the textarea for the Terms field.

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 1 Screenshot 110

    2. Edit the name and value of the fields. In my textarea, I added the terms that you have, but I also edited it in HTML.

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 2 Screenshot 121

    3. In the HTML editor of the textarea, I added "id=termsHTML" and change the cols and rows value.

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 3 Screenshot 132

    4. After saving, I navigate to "Setup & Embed" and get the full source code.

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 4 Screenshot 143

    5. Choose "Source Code" and copy the code there.

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 5 Screenshot 154

    6. I then pasted the code to my text editor, in my case it's Notepad++.

    First, navigate to style tags and I add this code:

    #termsHTML {

    overflow: scroll;

    }

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 6 Screenshot 165

    7. Next, scroll down at the bottom and add this code before the form ends.

     

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 7 Screenshot 176

    8. I then embed the edited source code to my website or a webpage.

    You can see the live form embedded to a sample webpage here:

    https://shots.jotform.com/charlie/scrollable_TOS_final.php 

    This should look like this:

    8.1 Unable to tick the checkbox.

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 8 Screenshot 187

    8.2 When you reach half or almost bottom of the terms an alert will show (this is just for code testing).

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 9 Screenshot 198

    8.3 The checkbox will then be enabled and be available to tick.

    Feature Request: Force user to navigate through the end of the Terms Conditions before agreeing on checkbox Image 10 Screenshot 209

    What that code does? The code by default disable the checkbox of "I accept..." field, the user then needs to scroll through the terms textarea and when he reaches the bottom or at least half of it, the checkbox will then be enabled.

    Please note: Please do check the IDs of each element, it may be different from yours.

    I hope this helps. Let us know if you need further assistance on this.

    Thank you.

  • Charlie
    Replied on November 28, 2014 at 9:02 AM

    Hi,

    Aside from the workaround I provided above, I have escalated your concern as a feature request for the widget Scrollable Terms. Our developers and technical team will take a look at this, you will receive a notification when an update has been made regarding if it has been considered for implementation. Unfortunately, I'm unable to provide an ETA or expected date to when we can receive an update, but rest assure that this has been already brought up to them.

    Thank you.