I know that page shouldn't crash any browser, really, but the crash happens as a result of poorly-written HTML (a missing </form> tag) that IE can't seem to handle.
The poorly-written HTML, however, is frequently generated by larger ASP.NET-based CMS systems (and occasionally SharePoint servers) that start the <form> in the header and don't close it on the page. This snippet is just a shorter example of the error, but is certainly not the only instance where this problem rears its ugly head.
That would be an example of yet more problems originating from MS products, then, right? I don't see why MS can't get this right. MS has the resources to produce a good product, but when it comes to the web, they fall on their faces.
Hey check your facts. I just tried with the RC build of IE. It never loaded the site but the browser didn't crash and the rest of the tabs are working fine.
Of course I can't rule out them getting it right in future releases, and I hope that they do. I was talking about what is out there in the MS ecosystem, today.
The thing is, web browsers are always going to have to deal with two kinds of people: The malicious and the incompetent. They both write web pages, and neither can be avoided completely.
And, when you get down to it, it's impossible to distinguish sufficiently advanced incompetence from malice. (This sentiment seems quite appropriate when discussing Microsoft's browsers.)
