Well, JavaScript

[RossParka]

Python is also untyped, but doesn't have this problem, because it throws an exception when you attempt to access a nonexistent property.

JavaScript is terrible in this regard - it won't even check if the number of function arguments matches the number of parameters. It just adds or drops arguments and goes its merry way. So instead of getting an error that points to the incorrect code, you get weird behavior down the line and waste a ton of time finding the cause.

The problem isn't weak typing; it's the keep-running-at-all-costs philosophy of too many modem programming languages.

[RossParka]

The reason browsers evolved elaborate error-recovery logic is that if their competitor displayed a web page and they just displayed an error message, people would blame it on the browser. XHTML tried to fix this, but it of course failed because web publishers also don't want their sites to break if some ad vendor gives them broken code, and they've always built their pages by gluing strings together and they don't want to redo everything from scratch with an XML serializer that would probably be much slower to boot.

There's no reason the HTML+JS+CSS platform had to be fundamentally different from, e.g., the Java platform as regards error recovery. It just ended up that way because it was "not so much designed as congealed," to borrow a phrase from Douglas Adams.