EW Resource

IE10 - Be Prepared

IE10 has three significant issues you need to be aware of:


1) Check your ASP.Net sites run correctly

If you are running ASP.Net sites, check that the servers have been updated with the latest browser information patch. If not they won't recognise IE10 and will treat it as a 'down level' browser and consequently won't render all the JavaScript that ASP.Net depends on.

It should be obvious if this happening because some ASP.Net functionality (postback events) won't work.

So for example, if you have a drop down list that triggers something else when the selection changes, this will fail. If in doubt, copy the code below onto a clean page of your own, upload it to your server and open it in IE10 (and another browser for comparison).

If you find PostBacks failing you'll need to contact you host company ASAP. If they don't understand or recognise the issue, refer them to this page.


This explains the issue and has links to the Hotfixes.


2) Switch off compatibility mode for intranet sites

If you locally preview a site that uses HTML5 and CSS3 features (placeholder text, round corners etc.) in IE10, using the EW Development Server or IIS, you may find that these features don't display.

This is because the default browser mode for intranet sites in IE10 is 'Compatibility mode'. You can change this in 'Tools - Compatibility View Settings' . Uncheck the 'Display intranet sites in Compatibility View' option.

Now you'll notice that there is also a setting 'Display all websites in Compatibility View'. What happens to your site if a user has this checked, intentionally or unintentionally? Your site won't display properly.

You can avoid this problem by forcing IE10 into it's highest or 'Edge' mode. You do this by adding the following meta tag to your pages or the DWT / ASP.Net MasterPage.

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

It's worth adding this to the existing IE Meta Tag snippets in EW V4.

3) IE10 on Windows Phone 8

The version of IE10 on Windows Phone 8 apparently has a bug which results in media queries not seeing the correct device width.

This post from Devhammer explains all. http://devhammer.net/responsive-design-fix-for-windows-phone-8-device-adaptation

I'd not noticed this on the WP8 Emulator which proves yet again that testing on real devices is essential.

Internet Explorer 10 Compat Inspector

Microsoft has created a 'simple to use' JavaScript utility to help detect compatibility issues with IE10. The following user guide shows you how to install it, use it and work with the results.