Loading Elmah in IE10 results in JavaScript errors

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Cause an error
2. Go to Elmah
3. Get JavaScript errors

What is the expected output? What do you see instead?

No errors should occur

What version of the product are you using? On what operating system?

Elmah 1.2.2, Win8, IE10

Please provide any additional information below.

If I load up the F12 tools, I can see that the document mode is IE7. Changing 
the document mode to "Standards" fixes the issue.

I looked into why I was seeing that and it turns out the code is hard coded to 
produce:

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

Elmah should produce

<meta http-equiv="X-UA-Compatible" content="IE=Edge" />

so that Elmah is always rendering at the latest standard.

The code for this is in ErrorPageBase.cs, but based on the comments it appears 
this was done on purpose

            //
            // In IE 8 or later, mimic IE 7
            // http://msdn.microsoft.com/en-us/library/cc288325.aspx#DCModes
            //

            writer.AddAttribute("http-equiv", "X-UA-Compatible");
            writer.AddAttribute("content", "IE=EmulateIE7");
            writer.RenderBeginTag(HtmlTextWriterTag.Meta);
            writer.RenderEndTag();

Is there a reason we are forcing output to IE7?

Original issue reported on code.google.com by dfried...@dragondoor.com on 16 May 2013 at 8:13

[GoogleCodeExporter]

I can't find the changeset that fixed this, but it appears to be fixed in the 
latest source, but broken in the latest release. Can we push a release?

Original comment by dfried...@dragondoor.com on 16 May 2013 at 8:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This also seems to break Glimpse. At the very least, it would be nice if it 
would only set one if there was not already one defined in the web.config.

Original comment by jasonken...@gmail.com on 17 Dec 2013 at 7:07

[GoogleCodeExporter]

This issue has been migrated to:
https://github.com/elmah/Elmah/issues/332
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 25 Aug 2015 at 8:25