On Tue, 01 Oct 2002 08:37:07 -0500, Sam Ewalt wrote: > On Mon, 30 Sep 2002 19:37:36 -0400, Glenn McCorkle wrote:
>> No, crashing is not good behavior for *any* program. >> (browser or otherwise) >> As for what NS or IE do..... >> I have NS for both Linux and for Win9x >> But... There is no way to test this exact circumstance on either of >> these versions of NS because neither of them has the exact same >> capability as Arachne. > True enough. But presumedly the bonehead who wrote the HTML that > apalled you so grievously at least viewed his or her creation > with IE. Now since bonehead HTML is still bonehead HTML, how come > it doesn't crash IE? Or maybe it does. But it's hard for me to > concieve of a deliberate web page that would crash every browser. > There's got to be lots and lots of invalid HTML out there. So how > do browsers avoid crashing everytime it runs into totally invalid > HTML? The HTML itself is not the problem. http://members.tripod.com/south.wind.kalyani/ This page does not crash Arachne when it is rendered and displayed on the screen. The problem arrises when we hit F6 to view the SRC of the page and then use the F7 search-in-page function to locate some particular text. It's when that 1,108 character long line is encountered during the search that the crash takes place. (Arachne has a max limit of 600 characters) The F4, F2 combo causes that line to be wrapped down to 3 shorter lines. These new lines no longer exceed the 600 character limit. So, the crash no longer happens when doing the F7 search. BTW, Either I mis-counted the first time..... Or thay have updated the page and made it even longer. I just checked and it's now 1,109. :(( -- Glenn http://arachne.cz/ http://www.delorie.com/listserv/mime/ http://www.angelfire.com/id/glenndoom/download.htm http://www.thispagecannotbedisplayed.com/
