Removal of Jquery Dependency

Woo! Tagging @Phillip here, this is something he’s been championing for a while here in the community.

Will this allow us to disallow submissions from certain domains for example?

Hi @Brian_Burns,

Thanks for the reply. It looks like the multi-step script that’s in use in your example is different than the one shared in this thread. Would you mind sharing the updated script so that we can test it with our forms?

Figured it might be an idea to try this avoiding the Shims you’ve put in place to make older pages work in this new system. The following is the older function we were using for page specific validation and the quick test function I put together… it appears to be working with the first page I tested this on… Going to continue testing…

 var isValidOld = function(page) {
    var fieldsArr = pages[page].split(',');
    var validateArr = [];
    for (var i = 0; i < fieldsArr.length; i++) {
        var x = fieldsArr[i].replace(/(#container_)/g, '').trim();
        validateArr.push('[name="' + x + '"]');
    }
    return lp.jQuery(validateArr.join()).valid();
};

var isValid = function(page) {
    var fieldsArr = pages[page].split(',');
    for (var i = 0; i < fieldsArr.length; i++) {
      var x = fieldsArr[i].replace(/(#container_)/g, '').trim();
      if (!document.getElementById(x).reportValidity()){ return false; }
    }
    return true;
};

[edit: Doesn’t appear to work for radio groups]

Hi Jess, We’ve been in regular communication with both our account manager and Rob over this. I don’t think our being on GMT helps with communications with this though. That email about the release was around 9:40pm GMT on a Friday suggesting a Monday release… there would have been radio silence from our end too 😉

I was kinda hoping that the issue with the shim would be fixed so that we wouldn’t need to change every single page we host.
Rob was kind enough to setup a test account for us so we could test the various scripts we make use of.
I have put together a working equivalent of the isValid function making use of the reportValidity method you guys are moving to.
This is our isValid for checking if a selection of field is valid so that you can make use of a next button to switch between different pages with a portion of the total number of fields in the form. There is both the original function and the newer function here so I am hoping this can help in your debugging of the Shim. 😉

I know you’re probably not even through your first coffee yet and your early reply is appreciated but it would be great if we could know what is going on with this before 10:30am PDT (5:30pm GMT).

 var isValidOld = function(page) {
    var fieldsArr = pages[page].split(',');
    var validateArr = [];
    for (var i = 0; i < fieldsArr.length; i++) {
        var x = fieldsArr[i].replace(/(#container_)/g, '').trim();
        validateArr.push('[name="' + x + '"]');
    }
    return lp.jQuery(validateArr.join()).valid();
};

var isValid = function(page) {
    var fieldsArr = pages[page].split(',');
    for (var i = 0; i < fieldsArr.length; i++) {
      var x = fieldsArr[i].replace(/(#container_)/g, '').trim();
      console.log(x);
      if (typeof document.getElementById('#group_'+x) !== 'undefined') {
        var y = document.getElementsByName(x);
        if (!y[0].reportValidity()) return false;
      } else if (!document.getElementById(x).reportValidity()){ 
        console.log("fail:"+x)
        return false; 
      }
    }
    return true;
};

Hi @TimothyDO, Rob told me he’s sent you an email to discuss this further, I think it would be best if you both discuss your particular situation in a separate thread. I’d like to ensure that no updates get buried in this thread.

Rob will be updating here with more info 🙂

WOOT, WOOT!!! 🤩

Is there an updated timeline on when this is getting rolled out?

Thank you @Rob!

I’m definitely keeping an eye on this! Thanks for bringing this to our attention @julien_level!

I think i’ve lost almost a day of trafic.

I’ve found that on a lot of my LP (and all variant) that people couldn’t add their phone number.
It looks like by default, all phone fields have been set to “validate phone number as american” while not being activate in the form parameters…
it took quite some time to change all form to set them up to 'validate phone number as generic".

I also had to desactivate the “custom validation” script that helped me make sure that people were entering french number (10 digits) as it doesn’t look like it’s working anymore.

I really love Unbounce but i think it’s time to really update the form parts to give more options naturally and depends less on script.

update : Wow i just tried my LP in Firefox and i get a white page after completing the form…
this is getting serious, i have to stop buying trafic for now.
here is my LP : https://www.eau-pure.fr/adoucisseur-sfte/

While you’re looking at the telephone field it’s not assigning type=“tel” either. So our custom validation built for this new version doesn’t recognise telephone fields… @Brian_Burns

I don’t believe these issues are related to this release. Your leads seem to have had the duplicate telephone rows for quite some time. As to the second issue, I can only speculate that it may be something to do with a firewall if it’s only affecting leads from within your company.