As a short term workaround, did you try disabling strict XHTML checks for the Administrator group?

I don't actually recall seeing that setting before. Time to go for a dig and see what I find... :-)

OK, I think I found them, but looking at how they're set, it would seem that they are already set to their lowest level - they're not something I've ever changed in my time using b2evo.

We'll publish a fix for allowing the http equiv shortly.

Additionally, in this case, should we make this meta a default in our bootstrap skins?

From a personal perspective, I'd be happy to have the 'Edge' tag as a default, but I'm not sure it would suit everyone. - you perhaps have a better idea of what your users are doing, or what they feel they need to support out there for their user base. Ideally, it would be nice to have a selectable option, but as a non-developer, I've no idea how much work that would involve for you.

Initially, the ability to just drop the meta tag into the header would be a good start and would work just fine for me. After that, I'm happy for things to take whatever you feel is the best course.

The custom area will accept http-equiv in v6.6.3.

Thanks Francois, much appreciated :)

Just thought I'd let you know that I've updated to 6.6.3 and the new meta tag went in fine. It's now showing as expected in Chrome DevTools on the skin I'm using.

Cool :)

We will have this by default in the HTML header in b2evo 6.7+

Will be in 6.6.4 actually ;)