Extra –> symbol on header

As I am facing exactly the same maybe I can assist here. At least on my site I have some inline js in the head (on my site added by Bad Behavior plugin) which is escaped by HTML comment tags <!– and –> inside the script tag:

<!-- Bad Behavior 2.2.15 run time: 17.091 ms -->
<script type="text/javascript">
<!--
function bb2_addLoadEvent(func) {
...
// --></script>

Minification wraps the script in comment tags and inserts a minified version afterwards:

<!-- Bad Behavior 2.2.15 run time: 17.091 ms -->
<!-- <script type="text/javascript">
<!--
function bb2_addLoadEvent(func) {
...
// --></script> -->
<script src='//some.domain/wp-content/cache/wpfc-minified/62...

Look at the closing </script> tag of the inline script: there you have the additional –>

For the time being I will modify the inserted inline code and delete the HTML comment marks – that should do the trick without causing other problems.

Indeed, it is the add2any script on javahonk.com showing the additional –> after minification:

<!-- <script type="text/javascript"><!--
var a2a_config=a2a_config||{},wpa2a={done:false,html_done:false,script_ready:false,script_load:function(){var a=document.createElement('script'),s=document.getElementsByTagName('script')[0];a.type='text/javascript';a.async=true;a.src='http://static.addtoany.com/menu/page.js';s.parentNode.insertBefore(a,s);wpa2a.script_load=function(){};},script_onready:function(){if(a2a.type=='page'){wpa2a.script_ready=true;if(wpa2a.html_done)wpa2a.init();}},init:function(){for(var i=0,el,target,targets=wpa2a.targets,length=targets.length;i<length;i++){el=document.getElementById('wpa2a_'+(i+1));target=targets[i];a2a_config.linkname=target.title;a2a_config.linkurl=target.url;if(el){a2a.init('page',{target:el});el.id='';}wpa2a.done=true;}wpa2a.targets=[];}};a2a_config.tracking_callback=['ready',wpa2a.script_onready];
//--></script> -->

Original code

<script> <!-- ... --> </script>

is “deactivated” by wrapping it in HTML comment tags:

<!--
<script> <!-- ... --> </script>
-->

Too bad the browser doesn’t understand these “double nested” comments properly…