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

0 Likes

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

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

11 Comments
Anonymous
Not applicable

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.

Victor,

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

Anonymous
Not applicable

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
Not applicable

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.

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>

This is coming in the Spring release.

Anonymous
Not applicable

This news is awesomesauce! Thanks!

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

Anonymous
Not applicable

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
Not applicable

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!