Integrated in sakai-10-java-1.7 #62 (See http://builds.sakaiproject.org:8080/job/sakai-10-java-1.7/62/)

Result = UNSTABLE

While I'm in favour of not supporting IE8 I think Sakai should be clear about this and not hide it in a ticket.

My vote is we move forward. If people are really concerned about IE8 then a patch could be added which warns and provides a instructions via JS popup to tell them how to disable compatibility mode. I don't think IE8 really matters enough to bother myself.

So given that there is an issue with rendering some tools in IE8 (compatibility mode) and not really able to control what the users settings are for IE if they are not in compatibility mode.
Given IE8's market share http://www.w3counter.com/globalstats.php
1 Chrome 34 20.71%
2 Firefox 28 13.04%
3 Safari 7 11.41%
4 Chrome 33 9.24%
5 Internet Explorer 11 5.56%
6 Internet Explorer 8 3.74%
7 Android 4 3.66%
8 Internet Explorer 7 3.29%
9 Safari 6 3.08%
10 Internet Explorer 10 2.60%

and that it works in IE 9+ should we move forward on this for Sakai 10 or wait?

From Stack Overflow (http://stackoverflow.com/questions/13342348/the-html5-doctype-is-not-triggering-standards-mode-in-ie8):

There’s a couple of settings in IE 8 that can cause pages to render in Compatibility Mode, regardless of the page’s HTML content or HTTP headers:

1. Page > Compatibility View Settings
– If “Display intranet sites in Compatibility View” is checked, then IE will render all sites on the local network in compatibility view. (This has happened to me a few times during development.)

– If “Include updated website lists from Microsoft” is checked, then IE will download a list of websites from Microsoft and render them all in compatibility view.

– If “Display all websites in Compatibility View” is checked, then, well, you can guess what happens.

2. Tools > Internet Options > Advanced > Browsing
– If “Automatically recover from page layout errors with Compatibility View” is checked, then IE will sometimes switch to compatibility view if it thinks a page’s layout is broken.

3. And, finally, if you navigate to a page and then click on Page > Compatibility View (or click on the compatibility view icon in the address bar), then that page will be rendered in compatibility view.

So, although it’s worth putting X-UA-Compatible in there and using a doctype like the HTML5 one (so that your intentions are clear), always check these settings first when testing.