X-UA Compatibility Meta Tag in JIRA 6 templates should come before any script tags

According to Microsoft, the X-UA Compatibility Meta Tag must appear in the Web page's header (the HEAD section) before all other elements, except for the TITLE element and other META elements. That implies, that it wouldn't work when it comes after the <script> tags for instance within the HTML header.

In JIRA 6 source a script tag comes before this tag,

<script type="text/javascript">
    if (!window.performance) {
        window.mpPerformance = {};
        window.mpPerformance.responseStart = new Date().getTime();
    }
</script>
<meta charset="utf-8">

<meta http-equiv="X-UA-Compatible" content="IE=Edge;chrome=1"/>

possibly making it useless and unable to perform it's intended function, which is to force IE to render the page with the chrome frame engine if installed or in the highest mode available.

Please note that in JIRA 5, this tag is positioned properly, as recommended by Microsoft. It is already clear that JIRA will not support compatibility view, but this tag was added to override the default settings for compatibility view from IE 8+.

Isn't there a possibility that we are having most of our rendering problems with compatibility view in IE with JIRA 6 instances and not so much in JIRA 5 because this tag isn't able to work as it should in JIRA 6, due to the wrong positioning?

If the X-UA Compatibility Meta tag can be made to work by looking into the position of this tag, users who for some organisational constraint cannot afford to disable compatibility view locally are more likely to be able to use JIRA 6 in IE, as they are using JIRA 5 without problems even though they are unable to locally disable compatibility view in IE.