31–40 of 94 posts
Earlier quoted context omitted.
I agree, it's unbelievable. End users don't care about incorrect markup, they care about their browser hanging.
Obviously this is a bug in IE that needs to be fixed and it's Microsoft's responsibility to ensure that their browser doesn't crash in invalid input, but end users don't actually care about the browser either (they don't even know what a browser is), they care about your site crashing.
Earlier quoted context omitted.
Looks like the crash doesn't happen if you provide the tag, so that looks like it. Edit with more info: Looks like removing any of the markup prevents the crash. "Removing the CSS, the div, the table, etc all cause this code to not crash IE"
The minimal variant with which I repeated the crash was: #a { margin: 0 10px 10px; } #b { width: 100%; } Removing the second td is enough to make the html not crashing on IE 9. The "crash" manifests itself in some kind of an infinite loop (one thread jumps to 100% CPU and stays so). Then the "recovery" mechanisms kick in, reloading the page, blocking again... :) Can anybody reduce it even more?
I think the most shocking thing is when you follow it through to the MSDN bug discussion—and you find people blaming the author for writing invalid HTML. Apparently IE doesn’t need to follow the robustness principle. http://en.wikipedia.org/wiki/Robustness_principle
I think the most shocking thing is when you follow it through to the MSDN bug discussion—and you find people blaming the author for writing invalid HTML. Apparently IE doesn’t need to follow the robustness principle. http://en.wikipedia.org/wiki/Robustness_principle
Agree. It's a horrible read. Good thing their marketing department hasn't caught up with this... yet
I don't see why it's such a big deal. Ya I mean it's kind of a dumb thing to cause a browser to crash, but I am sure any browser has a dumb thing here or there that will cause a crash. Seems like we're just trying to pick on IE here.
I'd agree. On a side note, took me about ten seconds of googling to find HTML/Javascript that reliably crashes firefox (but does not crash IE8). I expect Chrome would have similar cases where there could be something that causes crashes (at least, there are bug reports asserting this). (FYI here's some HTML/JS for the Firefox bug... Resizing the browser caused the issue to manifest in Win7 with FF 13.0.1:) http://www…
I don't see why it's such a big deal. Ya I mean it's kind of a dumb thing to cause a browser to crash, but I am sure any browser has a dumb thing here or there that will cause a crash. Seems like we're just trying to pick on IE here.
I'd agree. On a side note, took me about ten seconds of googling to find HTML/Javascript that reliably crashes firefox (but does not crash IE8). I expect Chrome would have similar cases where there could be something that causes crashes (at least, there are bug reports asserting this). (FYI here's some HTML/JS for the Firefox bug... Resizing the browser caused the issue to manifest in Win7 with FF 13.0.1:) http://www…
I don't see why it's such a big deal. Ya I mean it's kind of a dumb thing to cause a browser to crash, but I am sure any browser has a dumb thing here or there that will cause a crash. Seems like we're just trying to pick on IE here.
I'd agree. On a side note, took me about ten seconds of googling to find HTML/Javascript that reliably crashes firefox (but does not crash IE8). I expect Chrome would have similar cases where there could be something that causes crashes (at least, there are bug reports asserting this). (FYI here's some HTML/JS for the Firefox bug... Resizing the browser caused the issue to manifest in Win7 with FF 13.0.1:) http://www…
The most amazing part of this exercise has been analyzing the traffic trends. This page gets a crazy amount of traffic in Japan and China - I still can't figure out why.
It has also been a remarkable insight into the dysfunction that is Microsoft; I'll hear from some random Microsoft employee twice a year who became aware of the site and wants to fix it, after pointing to the closed "not a bug" thread on MSDN they all vanish (apparently keenly aware of how atrocious the IE team reacts to external interest/support.)
No? Anyone? Guess I'm wearing a black hat today.