It may or may not be the browser's fault, but it's most definitely related to the HTML being generated and not the back-end code (web browsers are strictly client-side - they more or less simply parse any HTML sent to them, regardless of the source).
While it's hard to say in this case, my bet is that it's Netscape 4 - a notoriously buggy, crufty browser - choking on valid HTML. Even if the HTML isn't strictly valid, a reasonably stable web browser shouldn't simply crash. At worst, it should throw up an error or display the page incorrectly.
We're not really directly supporting Netscape 4 any longer, as it has horrible standards compliance, has reached around 1% market, share and is continuing to decline (thankfully!).
It's fair to say that this is a cost/benefit issue for us. Supporting Netscape 4 often requires ugly hacks and bloated mark-up, and takes valuable time away from the development of features for the other 99% of the web. While there are certain cases where people with very old browsers are (unfortunately) limited in what browser they can run, there should be a limited expectation as to how long any company with finite resources can support it.
In any case, if you are able to isolate whatever portion of the HTML that is linked to the crash please let us know, and we'll forward it on to Solid Arity. The best way to do this is to use your browser's "Save As..." function to save the file to your hard-drive and find out what is causing the crash through a process of elimination.
- Jeff @ DreamHost
- DH Discussion Forum Admin