It’s just something you’ll have to live with, and another reason why trying to live and die by standards is stupid. Doing so often leaves some users without experimental features (remember -moz-border-radius?); even if others can’t see them, you can still improve your website for others.
The annoying thing is that I don’t need X-UA-Compatible on my web app. The only reason I need to use it is to stop Internet Explorer incorrectly telling people “this website is probably broken, you know. Click here to fix that.”
Websites, including html5boilerplate, appear to be telling people to use <meta http-equiv="X-UA-Compatible" content="IE=edge" />, which means to say “this is supported in every future version of IE, and current ones”. I don’t find that to be a sensible choice though. If you’re going to use this invalid meta element, why not actually have it work properly?
For Sound Tiger, I decided to set it to IE=9.
- Fairly old (Firefox 3 era) A List Apart article: Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8
- 456 Berea Street: X-UA-Compatible and HTML5