Conditional Logic : Condition Show/Hide is not working on Internet Explorer

  • Profile Image
    Asked on November 30, 2015 at 03:21 PM


    I have a form that has conditional fields, namely a field named "Subs" that is visible between 12:00 Noon and 7:30pm.  The form works properly in Chrome, however in IE it doesn't.  I have attached a screen shot that shows the same form in both IE (top image) and Chrome (bottom image) - these screenshots were taken only a couple of minutes apart (you can see the time in the lower right corner).  Refreshing the page, clearing the browser cache, etc., does not make a difference.

    I have tried other troubleshooting steps such as turning off pop-up blockers, turning off ad blockers, etc.  I cannot get the form to display properly in IE.

    In addition, I have a report that is viewed after a person clicks Submit - the report can also be viewed by a link I added at the top of the Form (click on the basketball).  The report also doesn't display properly in Internet Explorer.  The grid portion on the bottom shows up, but the bar graph on the top does not.  However the report also works properly in Chrome.  Both the form and the report were also tested in Safari, and worked properly.

    Any help you can provide?


  • Profile Image
    Answered on November 30, 2015 at 05:08 PM


    Thank you for contacting us.

    I tried loading your form on Chrome and Internet Explorer, I was able to replicate your issue, I can only see the condition working on Chrome, but not on Internet Explorer.

    I will escalate it to our developers and we will let you know any news via this thread.

    In regards to your second issue, I have moved it to this thread :

    I will assist you there.


  • Profile Image
    Answered on December 06, 2015 at 04:46 AM

    It seems that your last post did not came trough. I have checked our email log and found your reply, so I will quote your reply.

    "It has been several days since this issue was escalated.  How can I find out what the status is?"

    Unfortunately this issue is still not resolved. One of our developers is assigned to this thread and priority of this issue is set to very important.

    Once this issue is resolved we will inform you via this thread. 

    Thank you for you patience.