>Does Microsoft send out non-security updates for Internet Explorer 9 for those who are unable or unwilling to update to the latest version?

A crashing bug in a browser is usually considered to be a security risk, so this wouldn't be a non-security update.

Not always. Depends on the details of the crash. This particular case is actually a hang.

Unable to reproduce in MSIE10:

http://jsfiddle.net/4Zukm/

That code won't kill it, it seems to need a width and height, see this one:

http://codepen.io/beeglebug/pen/ntLbv

Just wanted to make sure this CodePen breaks IE9 (before we confirm whether its fixed in IE10):

Confirmed kills IE9 9.0.8112.16421

It kills the page for me, but not the whole browser. Same build.

Doesn't kill IE10 on my box. V: 10.0.9200.16521

Microsoft should claim "We don't have Something like bugZilla". OR We are unable to reproduce the bugs you have claim.

Huh they do:

http://connect.microsoft.com/directory/accepting-bugs/intern...

Hello hp50g,

Thanks for your link

I have used http://webmatrix.uservoice.com/ too much. Search for google on this site with "Kristina". You found a lot of post written by me.

I just hate it because I can't gave it to fellow guys work on Linux and Mac. Secondly When I tried it it's crash too much. I write a lot of post their but atleast finally move to Sublime text 2.

I'm guessing you're using Windows 8, but suspect that the bug still crashes MSIE10 on Win7. The two browsers look the same, but I suspect there are some drastic differences between their innards.

It doesn't crash IE10 on Win7

MSIE10 on Windows 7 here... works fine.

It's available in the Windows Update dialog, but it's not selected by default.

I think that's pretty much bull... it should be checked by default... when you choose to include recommended updates with important ones, it should include IE10 in that list. It's bad enough that IE10 a year ago was close to current, that it took nearly a year to release the thing, now they don't even push it out. IE9 should be effectively dead now, but it's not.

They actually do include non-security "GDR fixes" in cumulative security updates. See the KB article associated with them. For example a MS10-xxx security update fixed the "operation aborted" appendChild problem and made it actually work.

Just a heads up for anyone thinking of ugrading to IE10, it breaks several sites including FedEx, at least on Win7.

The great thing about IE is that is backwards compatible. A website can automatically trigger IE to render in a specific version using metadata tags. I believe it can even go so far as to force it into compatibility mode by default for the website.

For websites that don't do this you can create a special list which can even be managed by group policy.

I'm always very frustrated when organizations choose not to upgrade for "compatibility" reasons. That's baloney. They're just too lazy to properly configure their systems.

There are features in oldIE that you can't bring forward via compatibility mode. I don't have a full list handy, but XML Data Islands come to mind as something that has legitimately anchored companies I've worked with to IE6 (and not because I wrote apps using the XML Data Islands, for the record!).

It's not very hard to update that code to use non-legacy approaches, but it's a massive undertaking to even determine what code needs to be updated in some companies where hundreds of one-off apps are created and then never maintained, much less do the work to update them.

>XML Data Islands come to mind as something that has legitimately anchored companies I've worked with to IE6

Looking at the pages describing XML data islands, it looks like it would be a day's work to make a shim for other browsers using jQuery.

What other "features" would you miss out on by not using IE6?

The problem isn't fixing that in one application. It's determining which features are affected, how many of your enterprise's hundreds of internal apps are affected, and then putting together a plan to fix all of them. Often, no one has touched these apps for years, and the people who were familiar with them are long, long gone.

Even if it turns out that none of a company's applications need to be updated, the cost of determining that is far from zero. In larger companies it can be difficult to successfully make the argument for that cost.

XML data islands works even in IE10 in IE9 and older modes: http://msdn.microsoft.com/en-us/library/ie/hh801224%28v=vs.8...

Two of my clients were never able to get that to work in IE8 or IE9. Thankfully, we haven't needed to try in IE10 because we've finished a site-wide revamp at both to bring their apps current.

I've seen a couple mentions about that (Gmail being another site it breaks). What seems to be going on, and I don't have a Win7 machine to test on myself, is that something's causing IE10 on Win7 to incorrectly switch to compatibility mode on the affected sites. If you use the dev tools to switch back to IE10 standards mode, those sites work normally.

I think they should be able to fix that soon via Windows Update. I remember Windows Update made a change a few years ago that was switching all localhost:// addresses to compatibility mode, so there's probably an easily updatable list of sites that this happens automatically on.

IE10 on Windows 8 is not affected.