Skip to main content

UPDATE AApril 2, 2019]: This change has been deployed! Unbounce is no longer dependent on jQuery for form submissions 🙂



UPDATE AApril 1, 2019]: The code change to remove our dependency on jQuery will be released this coming Wednesday, April 3rd.



UPDATE AMarch 28, 2019]: This release has been pushed back to later in the week to allow time to address some issues with a couple of community workarounds that would have broken with this update. This deploy will not be going out today (Monday, March 25th). Updates will be posted here when a new release date is determined.



Hi everyone, some exciting news to share 👋


Some of you have commented in the community about the use of jQuery on Unbounce landing pages and today we’re here to share an update (jQuery is a Javascript library we used to power Unbounce’s form submissions). As of Monday, March 25th, we’ll be rolling out an update to remove this dependency.


What does this mean for you?


Form Improvements

By removing the dependency on jQuery, your Unbounce forms will leverage your visitor’s web browser to power any form validation errors. This means a much deserved facelift to form errors and a more robust method for alerting visitors to any issues with their forms. Basically, any form validation errors will look a lot better.


This change will allow for faster iteration and a more scalable code base that will enable us to make future updates more efficiently and with less risk. Instead of using an older version of jQuery (1.4.2) to handle submissions, Unbounce forms will instead use vanilla javascript moving forward.


FAQ


Will this impact custom code on my page that uses jQuery?

We’ve tested to make sure that Unbounce features continue to function as expected, however, since there’s no way for us to test all custom scripts, there’s a chance that some custom code may be impacted. We rely on the feedback here in the community, so if you notice your custom code functioning differently, please let me know and I will relay it to our product team. The removal of the dependency on jQuery has also been tested against the majority of community tips and scripts (https://community.unbounce.com/c/unbounce-tips-and-scripts) so if you’re using any of those, you should be all good. We recommend double checking your custom code just to be sure.


Will workarounds from the community using jQuery still function?

Popular workarounds involving custom validation rules and messages will still function as expected as will the workaround to execute code on form submission. Despite thorough testing however there is still a chance that fully custom coded solutions involving form submission may be impacted as we cannot account for 100% of custom code solutions when testing. We recommend double checking your custom code just to be sure.


Is Unbounce removing jQuery from my already published pages? What if I have other functionality that depends on jQuery?

Not to worry – this update only affects the use of jQuery for form submissions. If jQuery is included on your page with either custom code or by selecting the 1.4.2 box in the builder, it will continue to load on live pages as before. If you are intentionally including jQuery on an Unbounce page it will continue to load as expected.


Native Chrome Validation Error


image-20190208-012358


Want to take your Unbounce landing pages, popups, and sticky bars to the next level?


:spinbounce: Check out the Ultimate List of Unbounce Tips, Scripts & Hacks

you may be right, but strangely i’m at home and he is at the office.

I’ll deal with that after 😉

thanks

Will take a look. Thanks @TimothyDO

@julien_level Really quick dirty fix for the telephone issue… Assuming your field is called “telephone”…

$(’#telephone’).removeAttr(‘pattern’);

document.getElementById(‘telephone’).type = “tel”;

@TimothyDO

I took a look back at an older version, released Feb 6th, and telephone fields were not being assigned type=“tel” so I don’t believe this is something new. Could you please provide a specific example if you believe this was just changed?


Thanks

I had you (unbounce) hook up with a thirdparty validation company to come up with new versions of the scripts they provide their customers, the majority of which make use of your service.

The code you came up with between yourselves included the following…


$(‘inputntype=tel]’).bind(‘change’, function(e) {


Which would denote that you (at least at one point) thought that you’d be using the html5 tel input type…

Thanks @TimothyDO for the quickfix.

As we are approaching the end of the day here in France, i’m gonna wait until tomorrow to see if the expert from Unbounce fixes everything.

Hey folks! Please let me know if I should start a separate conversation. I’d like for each of you to have the answers that you need, but I also want to make sure that updates don’t get buried here in this thread.


It might be faster if we set up a quick meeting to make sure we’re all on the same page. 🙂

Hey all,

We’ve decided to roll back this release temporarily due to an issue that has come up with GTM. If you republish your pages you will have the previous version with jQuery included. Before rolling forward again we’ll look to address as many of your issues as possible and will update here when we have a new release plan.


Thanks for sharing your issues here!

Any update on when this re-release is?

@TimothyDO,


We’re currently testing the fixes. They will most likely be deployed in the next few days baring any issues uncovered. A more concrete release plan will be established today and we’ll update here.

Might be an idea to warn the community of the release date on this new release…

Hi Timothy,


I’ve created a new post here so that folks won’t need to scroll through the comments section to see updates. 🙂


-Jess

Reply


Terms & ConditionsCookie settings