At sussex.ac.uk anything within the domain of sussex.ac.uk is seen by student & staff machines as being part of the intranet.
This causes a strange effect in IE9.
Sub domains e.g. moodle.sussex.ac.uk are rendered by IE9 as IE7....
But we know how to fix this right?
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
Like most good developers we are setting some browser specific classes and ids on the html tag using conditional comments -
[if lt IE 7] , [if IE 7], [if IE 8], [if gt IE 8] etc...
and we were doing this before setting X-UA-Compatible.
The effect was IE9 defaulted to the IE7 view for intranet sites on seeing these conditional comments, and before getting to the X-UA-Compatible.
If your doing any IE conditional comments, set the X-UA-Compatible first.
It's the opposite of best practice in html5boilerplate.com and other guides, but it did the job for us.
Be interested to know if anyone has any other methods of dealing with this?