IE9 and Forms | Community
Skip to main content
T
Tom_Kerlin2
Level 7
December 10, 2015
Question

IE9 and Forms

  • December 10, 2015
  • 2 replies
  • 3420 views

Hi all,

I read in a previous post that IE9 is no longer supported when redirecting a form. I'm worried because I can't control which browser somebody uses when they fill out a form and click submit.  The form/landing page redirects just fine in Chrome and Mozilla.  Has this been an issue for anybody else?

I appreciate your feedback.  Would like to know if there is a way to work around this. 

Thanks, Tom

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
December 10, 2015

This is not correct.  IE9 is no longer supported for using the Marketo application, but is fully supported for user-facing content like landing pages and forms. Have you actually seen this occur, or is this just hearsay?

T
Tom_Kerlin2Author
Level 7
December 10, 2015

Hi Kenny,

I imported myself as a test and registered but in internet explorer once I click submit on form it won't redirect to thank you landing page like it's supposed to.  But it works in Chrome and Mozilla.

Tom Kerlin
Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
December 10, 2015

There's likely some conflicting javascript on your page causing an error during the click or the submission.  If you share a link where you're seeing this, we may be able to help you find the issue.

Robb_Barrett
Robb_Barrett
Level 10
December 17, 2015

I was having some issues with the way IE was displaying pages and how forms were handled.  I places this piece of code in the header of my landing page template

<meta http-equiv="X-UA-Compatible" content="IE=edge" />

One of the issues I was experiencing is that Marketo uses a "foreach" loop in some of it's form script and IE doesn't recognize the "foreach" loop. Also, the CSS was being interpretted incorrectly.  This code fixed all of the issues.

Robb Barrett
    A
    Anonymous
    December 17, 2015

    We have run into this too recenlty.  We added <meta http-equiv="X-UA-Compatible" content="IE=11; IE=10; IE=9; IE=8; IE=7; IE=EDGE" />

    Note, edge alone does not cover all IEs out there.

      Terms & ConditionsAccessibility statement

      Loading footer...