{ prefill } mktoPreFillFields script should be injected further down in <head>

Anonymous · ‎08-17-2015

When Marketo's form prefill feature injects its <script> tag as the first child of the <head> tag, it confuses Internet Explorer's compatibility-mode detection and causes pages to be rendered in old IE modes (ex: IE7 emulation).

By default, please skip over both <meta charset> and <meta http-equiv="X-UA-Compatible"> to ensure proper cross-browser support.

See also:

Marketo, Internet Explorer, X-UA-Compatible, mktoPreFillFields

Anonymous · ‎08-24-2015

We are forced to workaround this issue by disabling the "prefill" feature when creating landing pages. (Edit Draft -> Menu -> Form Settings -> uncheck the "Enable Form Prefill" option)

Since we feel strongly about the "customer service" value-added by having the prefill feature, it is an urgent issue to resolve by fixing the placement of the injected "prefill" JavaScript.

Justin_Cooperm2 · ‎11-12-2015

Victor,

I've logged this with our engineering team. I'll work on changing this functionality for you.

Anonymous · ‎12-08-2015

Justin,

I'm looking forward to the day that the functionality fix is implemented and released to production. How will I know about it once that happens? *looks for a way to get email notifications*

Anonymous · ‎03-07-2016

I'm running into the same problem with our IE users. Would love for this script to be injected towards the bottom of <head> instead of the top.

Justin_Cooperm2 · ‎03-08-2016

I have someone working on it. Planning to add an option in Admin that will let you control whether it goes at the beginning or end of the <head>

Justin_Cooperm2 · ‎04-06-2016

This is coming in the Spring release.

Anonymous · ‎04-06-2016

This news is awesomesauce! Thanks!

Justin_Cooperm2 · ‎06-14-2016

Done! Go to Admin > Landing Pages > Settings and choose Inject Prefill Script At End Of Head

Anonymous · ‎10-26-2016

Wow - I am SO glad I found this article - been having an incredible annoying issue with IE and my landing pages, just for the users at our company, and this appears to have solved it.

Anonymous · ‎10-26-2016

I know, right? Hours of trial-and-error testing went into making the initial report. The "fix" really should be "ON" by default, though. I just don't see any reason why they'd want it at the TOP of <head>, ever.

Anyway, please share the good news to all your user groups!