Bring Down Internet Explorer In Six Words
Marcion writes "Some handy Japanese guy called Hamachiya discovered a bug in Internet Explorer. Under certain conditions, an asterisk when used as a wildcard can crash IE as soon as the user attempts to go to another page." The article claims the "five HTML tags and a CSS declaration" crash IE7 as well as IE6, but I couldn't get IE7 to fail. This page says that as of June, IE6 was at about 37% market share and IE7 under 20%.
I didn't think I'll see the day when browser crashing on something would be a newsworthy item. We - the industry - have made improvements in the last years I guess.
...then here's a word perfect translation of that article (courtesy of Babelfish).
Erm... then again, maybe not.
(If you liked that translation, you might enjoy Babelfish's attempt at Slashdot.jp.)
"Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
It indeed crashes IE here... Windows 2K3, IE7
Post
A
Crappy
Article
On
Slashdot
:(){ :|:& };:
TFA's servers aren't responding at the moment, so this might be included, but has anyone tried this with non-IE programs which use the Trident layout engine?
If it's Trident that's bringing down IE, then you're looking at HTML code that could also bring down Windows Media Player, several versions of Outlook and Outlook Express, MSN Messenger, Steam (from Valve), and other applications which use it to render web pages. I think at least some versions of Winamp used trident as well, but I'm not sure about that.
200 HP? Is your shit a 20th level Barbarian or something?
Yeah, but don't you think w3schools would be a bit biased? W3schools is a site full of tutorials and information for developers. Developers tend to prefer FireFox due to its robust plugin system and some of the excellent plugins for that system (Firebug, Web Tools, etc.) so I'm not surprised that FireFox has a higher rate of use on such a site. In fact, I am surprised that it's not higher!
It's not a crash, per se. It's a forced closure due to an illegal operation of one component of the browser with code in mshtml.dll.
An exception was thrown that was not properly caught. The error is caused by improper error trapping. Otherwise, the browser would just render things improperly or claim there was an error on the page because it doesn't properly parse and render the style tag.
The road to tyranny has always been paved with claims of necessity.
If you include it in the body of an HTML mail message.
Pre-tell then, what is a crash?
;)
When an exception is thrown and is not properly caught. The error is caused by improper error trapping. This is a classic "crash."