On Wed, 14 Feb 2001 18:12:55 -0500, L.D. Best wrote:
> Sam,
> Well, since the only browser I have *is* Arachne, I obviously was able
> to access the page. And since I already proved to my satisfaction
> that the problem was specifically related to graphics [try the page
> *without* automatic image download], and even more specifically to
> graphics being called via javascript, putting the whole javascript up on
> the list was not only bandwidth waste but also waste of time. The
> primary javascript does not, in any manner, interfere with Arachne
> 1.70v3 access to the site.
> l.d.
> P.S. Clue to all: If a page crashes Arachne, first thing to do is
> *disable* automatic image download.
L.D.:
Of course I already know about all this business of disabling automatic
image download when a page causes a system lockup. Some people haven't
learned about it yet and it was good that you had posted this reminder
notice. Instead of turning off images with Arachne I decided to revisit
the page with a text browser instead, being Lynx386. When Lynx386 freezes
up you can usually escape from the program with a CTRL + C instead of
giving it the three finger salute. For this reason I prefer to use
Lynx386 to access web pages known to be troublesome. I wish Arachne had a
good breakout feature like Lynx386. The JavaScript was the problem
because it was calling for graphics to be loaded in some way not tolerable
to Arachne. If you were not already aware of the problem at that page
before going there you might visit the place with images turned on. I went
there at first with images on to see if I could verify whether it is indeed
an Arachne crash site, as reported. It most definitely is. JavaScript is
to blame. Whether it was the primary or the secondary JavaScript is
irrelevant.
Sam
-- See our Big Gizmotimetemp at
-- http://banners.wunderground.com/banner/gizmotimetempbig/US/VA/Mt_Jackson.gif
