>>88
You put a Touring-complete language in a browser, you should expect shit like that to happen.
No, you put a Touring-complete language in a browser, I expect since it's interpreted and all, it'll be interruptible and not block. Of course due to retro-compatibility (and the fact that Web developers wouldn't get it right in any case), everything has to block because execution is expected to be fully synchronous.
Chrome gets it right by accident, the tab process will hang until you terminate it or close all the tabs that belong to it. It might give you the wrong illusion because it keeps a backing store of the last shown page, but it still hangs.
Did you know that until recently there was a way to do a blocking network request via JavaScript? It'd block the entire browser until completion. If the network died without explicit error, the browser would be locked up forever.
Also: have you noticed pages that freeze the browser for one second or so when you click a link? These are pinging back home to see which link you followed. To give the ping time to travel across the network (it'd be cancelled upon leaving the page), they spinlock in JS for one second. They might have started to do this in response of the "bug" in the previous paragraph being "fixed". Remember this the next time one of these faggots cry about adblocking. This kind of people needs to die.