AnsweredAssumed Answered

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

Question asked by 4d5b680a0ebddad4b17bf819274dca198b7cd2b0 on Aug 17, 2015
Latest reply on Aug 17, 2015 by 4d5b680a0ebddad4b17bf819274dca198b7cd2b0

I've been developing this as my standard start for web pages:

 

<!DOCTYPE html>

<!--[if lt IE 7]>      <html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]-->

<!--[if IE 7]>         <html class="no-js lt-ie9 lt-ie8"> <![endif]-->

<!--[if IE 8]>         <html class="no-js lt-ie9"> <![endif]-->

<!--[if gt IE 8]><!--> <html class="no-js"> <!--<![endif]-->

<head>

  <meta charset="utf-8" />

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

 

Unfortunately, Marketo outputs something completely different:

 

<!DOCTYPE html>

<html class="no-js"><!--<![endif]--><head>

<script type="text/javascript">

var mktoPreFillFields = { ... } /* an array of prefill data */

</script>

  <meta charset="utf-8" />

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

 

  1. Why would Marketo mangle the multi-HTML-element section? Can it be fixed to not do that?
    • I'm also open to the idea of using a marketo-specific workaround.
  2. Why does Marketo insert the mktoPreFillFields script as the first child of <head>? Can it be fixed to insert that at the end?

Outcomes