Anyone have trouble with IE 10 on Windows 8?

Has anyone run into issues running the Sitefinity Editor with IE 10 and Windows 8?

I am running into an issue now that *may* be caused by the browser version / Sitefinity version incompatibility.

I am running 5.0.2523, Windows 8, IE 10, VS 2010 SP1 and the issue only occurs when I go to edit a page. I get some JavaScript errors that prevent the page from loading. So far the error is not occurring in Firefox nor Chrome.

"Unable to get property 'documentElement' of undefined or null reference Error"
The issue may be related to this RadControls forum post:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/error-in-ie-10-due-to-telerik-dlls-version-2009-2-826-35.aspx 

I am hoping to upgrade Sitefinity to a newer version soon, but have quite a bit of testing to complete before we can upgrade the site. I am afraid to upgrade until I isolate the specific cause of the issue. (don't want to compound the problem with upgrades until I determine that is the appropriate fix)

Thanks all,
Dan

When I suspect an IE version issue, the first check is usually to <F12> for the developer toolbar, and then test different browser & documents modes - I am assuming this is still there in IE10?

Hey Danny,

Just tested it with a 5.1.3270 site, browsed with both IE10 'Metro' and regular from a Windows 8 machine and seeing the same message, although it did function properly (image widget/content widget add/edit on a page).

@Jochem
Perhaps the $telerik static client object ? 
http://www.telerik.com/help/aspnet-ajax/telerik-static-client-library.html

As far as I know, it doesn't have a 'isIE10' property yet.

@MB,

Yeah, so its very likely that IE10 'Backend' support won't come till end of the year.
One thing I noticed though earlier is the fact that IE10 reported wrong doctype declaration on the console output of the Developer Tools.  

Haven't checked it again, but if that's the case, IE10 could be defaulting to quirks-mode and jQuery has never supported/worked properly in Quirks-mode...

Jochem (and all),

You guys are awesome. Thanks for the help on short notice. Yes, it does appear to be an IE 10 back-end incompatibility. I appreciate your confirmation so I know it's not just this workstation. It's easily worked around at this point as all of my staff members savvy enough to be running Win8, also are running a second (supported) browser on their machine such as Chrome or Firefox.

I have also heard that 3Q will attempt to support IE 10. I hope so, it's a very good browser - especially for development work.

Have you tried forcing the compatibility level on the base template/masterpage ?

Oh, of course I completely missed the BACK-END part of the problem... which makes my comment complete nonsense (as usual).

MB: No problem, good suggestion that provides a decent work around. If I enter the F12 tools of IE 10, and then set the browser mode and the document mode to IE 8, it works as it should.

Setting IE 9 for both browser and document mode also works.