On Sat, 28 Sep 2002 22:05:09 -0400, Glenn McCorkle wrote: >> I was able to duplicate exactly what Ron described.
>> Medium news...... >> It's not a new bug. >> I tracked it all the way back to the beginning of "search in page". >> If you get this as an individual mesasage (not in the digest), you'll >> see from the mailer line in the header that I'm using v1.40;final_beta >> That's when F7 or / was first enabled for searching in the page. >> (just crash her a few minutes ago with the procedure outlined by Ron) > I am not going to spend even 1 more second trying to fix it. > Over 4 hours is more than enough time to waste on such a STUPID > person as the one who did THIS !!! This brings up once again what a well behaved browser should do when encountering "bonehead blunders" in HTML. I would like to suggest that crashing and locking up is not good behavior. Given the nature of the web any browser will encounter "bad HTML" that does not conform to accepted standards. What does Explorer or Netscape do something like this? Crashing doesn't seem like an expedient procedure for Arachne does it? Sam Ewalt Croswell, Michigan, USA -- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
