What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Conditions with "Contains" and "Does not contain" do not work in IE8Asked by cgorham on May 11, 2015 at 04:41 AM
I have three Show/Hide conditions on my form, which work fine in Chrome, Firefox and IE9+. Unfortunately, many of our expected users are still stuck on IE8.
Through testing, I've found that all the conditions work fine except for the ones using "Contains" and "Does not contain". The form needs to show an error when the user enters an email address of the type "@student.uwa.edu.au" (just that specific server).
IF Email address CONTAINS "@student.uwa.edu.au" THEN SHOW Error message;
IF Email address DOES NOT CONTAIN "@student.uwa.edu.au" THEN HIDE Error message;
In IE8, in the first instance the message is never shown. In the second, it is always shown.
In IE8, it seems that the "Contains" and "Does not contain" tests always return a False result.
Is there a workaround/fix for this behaviour, or another way of using conditions to achieve the same result?
contains workaround conditions conditional logic
I took a look at it and it seems that it is not working for some reason, just as you have mentioned it. Now what does work is if you alter it just slightly to check if the email address ends with it.
Since you had this check in your conditions: @student.uwa, then I made the change to it like so:
This way it will work even in IE8
You can test it here: http://form.jotformpro.com/form/51304206773954
Do let us know how it goes.
Thanks Ben, that's an excellent workaround - it seems so obvious in hindsight!
Could I ask that this thread be updated once the "Contains" condition behaviour is fixed?
I am glad to know that my colleague's workaround worked for you.
Let me connect with my colleague on the issue of "Contains" condition. We will update your here.