But any bit of trivial JavaScript code can crash a certain class of browser (the class without independent threads) -- it doesn't require even a small bit of cleverness.

It's just not newsworthy, and it's a public nuisance to post such examples -- I mean a working example, as opposed to an inert code listing.

I am sorry, but I found the code behind it interesting so posted it. I put it on jsfiddle! If you were smart enough, you could have accessed the html behind the page easily.

like this: view-source:http://fiddle.jshell.net/n3Wa3/show/light/

OR

http://jsfiddle.net/zalun/n3Wa3/embedded/html/

My point being, browsers should be able to recover from such code. What if some site's ad code has this in it. It shouldn't be able to crash my entire browser.

>> it's a public nuisance to post such examples -- I mean a working example, as opposed to an inert code listing.

> I am sorry, but I found the code behind it interesting so posted it.

You should have posted a listing, not a working copy. That would have been the civilized, non-destructive thing to do.

> If you were smart enough, you could have accessed the html behind the page easily.

I did. But if you were smart enough, you would have done that and avoided performing an unscheduled test of the less technically skilled visitors' browsers ability to handle broken code.

> My point being, browsers should be able to recover from such code.

Why not set your car on fire? A modern car should be able to tolerate the flames, right? Where's your sense of adventure?

You just aren't thinking. This is a public forum visited by people representing all levels of skill.