Marketo landing page forms NOT showing in IE 11 or Edge | Community
Skip to main content
Gary_S
Gary_S
New Participant
January 29, 2019
Solved

Marketo landing page forms NOT showing in IE 11 or Edge

  • January 29, 2019
  • 1 reply
  • 4337 views

We create Marketo landing pages on subdomains and noticed the forms do NOT show up in IE11 (or Edge). We contacted Marketo and their response was that there is customer code in the Template (bootstrap) that could be affecting it, and also that there is custom CSS on the form that could be affecting it. They said it's beyond their scope of support to help with code issues.

So, we created a test template/landing page/form using clones of the ones that didn't work and I did the following:

1. I removed basically EVERYTHING from the Template source code, other than the form code. So there is no longer ANY custom code.

2. I removed ALL Custom CSS from the form

Naturally, the form still doesn't show in IE11 or Edge.

Below is the URL of our now stripped down test form. I will go back to Marketo support with this same info but they are likely to continue to not be helpful.

Anyone see anything that I still might have overlooked?

https://go.spirent.com/WBR---ABM-Verizon-Preparing-For-5G---Dec-2018_TEST-REGISTRATION-PAGE-jr-1-29-2019.html

FWIW, in Edge's console, this error seems to be a problem: SCRIPT438: SCRIPT438: Object doesn't support property or method 'append'

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

OK, first of all, this doesn't only have problems in IE 11 or Edge. It also doesn't work in Chrome < 50 (at least).

1. I removed basically EVERYTHING from the Template source code, other than the form code. So there is no longer ANY custom code.

That's not true at all. You can easily see that you're still loading custom JavaScript code, and that the error is in that custom code.

You're loading 6 additional remote JS files from within a Rich Text area:

https://code.jquery.com/jquery-3.3.1.min.js
https://go.spirent.com/rs/627-MTZ-252/images/fontASM.js
https://go.spirent.com/rs/627-MTZ-252/images/date.format.js
https://go.spirent.com/rs/627-MTZ-252/images/chkDate.js?v=6
https://go.spirent.com/rs/627-MTZ-252/images/captchaTest.js?v=5
https://go.spirent.com/rs/627-MTZ-252/images/passKey.js?v=2

Look closely at the second one, that's where at least one of your bugs originates.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
January 30, 2019

OK, first of all, this doesn't only have problems in IE 11 or Edge. It also doesn't work in Chrome < 50 (at least).

1. I removed basically EVERYTHING from the Template source code, other than the form code. So there is no longer ANY custom code.

That's not true at all. You can easily see that you're still loading custom JavaScript code, and that the error is in that custom code.

You're loading 6 additional remote JS files from within a Rich Text area:

https://code.jquery.com/jquery-3.3.1.min.js
https://go.spirent.com/rs/627-MTZ-252/images/fontASM.js
https://go.spirent.com/rs/627-MTZ-252/images/date.format.js
https://go.spirent.com/rs/627-MTZ-252/images/chkDate.js?v=6
https://go.spirent.com/rs/627-MTZ-252/images/captchaTest.js?v=5
https://go.spirent.com/rs/627-MTZ-252/images/passKey.js?v=2

Look closely at the second one, that's where at least one of your bugs originates.

Gary_S
Gary_SAuthor
New Participant
January 30, 2019

Ugh, I removed custom code from the Template, but didn't realize there was other custom code in that Rich Text field in the Form itself. Thanks so much for pointing that out, I really appreciate it. I'll have to figure out now if that bit of JavaScript is necessary and if so, how to rewrite it to work properly.

Thanks again!

N
Nainsikala_123
New Participant
October 1, 2020

Marketo Munchkin VisitWebPage Activity is not showing in Markto Activity for IE11.

Although, visitwebpage request is success.

For other browsers it is working perfect.

Terms & ConditionsAccessibility statement

Loading footer...