Javascript and Netscape

[angweav]

http://www.rootsweb.com/~txpanola/index1.htm

The link above is the link to all my problems. :D

My problem is that people running Netscape4.7 cannot access the page because http://www.rootsweb.com/~txpanola/ converts to http://www.rootsweb.com/~txpanola/outline.js and then gives them the prompt File not found on server.

How can I make this page compatible with IE and Netscape?

**NOTE: the link http://www.rootsweb.com/~txpanola/ is no longer in javascript. I moved the page to http://www.rootsweb.com/~txpanola/index1.htm but if I can resolve my problem I want to move the index1.htm page back as the main page of my site.

[gil davis]

because http://www.rootsweb.com/~txpanola/ converts to http://www.rootsweb.com/~txpanola/outline.js and then gives them the prompt File not found on server.Then you'll be even more delighted to know that your page caused my browser to crash.

Is that file on the server? I couldn't find it manually. Did you name it something else, or is it capitalized?

[angweav]

Someone made the template for me and I plugged in my information and then uploaded the page. So I do not have an outline.js file on my server. To be quite honest, I have no clue as to what a *.js file is. I didn't even realize there was a problem with the page until my partner on the website brought it to my attention.

I am attaching the txt file of my code of the page the page in question.

[khaki]

Hi angweav...

I viewed your page/sourcecode (Netscape7... with no problems) and I notice that the following section appears to be causing the problem:
<script language="JavaScript" fptype="dynamicoutline">
<!--
function dynOutline() {}
//-->
</script>
<!-- hide from older browser<BR><script language="JavaScript1.2" fptype="dynamicoutline" src="outline.js">
</script>
<script language="JavaScript1.2" fptype="dynamicoutline" for="document" event="onreadystatechange()">
</script>//-->

It just doesn't seem to have any purpose (other than throwing errors :eek: lol)..

Try taking that out and making sure that everything runs without it (it should).

By the way... I really like your menu links (esp the colors)!
I'm gonna swipe 'em :eek: :rolleyes: lol

;) k

[gil davis]

Originally posted by khaki
I notice that the following section appears to be causing the problem: ... It just doesn't seem to have any purposeThis is one way to disable a function in an older Netscape browser. By specifying the version of javascript in the script tag, Netscape will only load the script for a language that it recognizes. For example, NS 2.0 will recognize the language="JavaScript" and load it, but will ignore the script inside the tag specifying language="JavaScript1.2". Things are read sequentially, and if a subsequent script has a function by the same name, the newer browser would replace the first one read by the "newer" one.

[angweav]

Originally posted by khaki
Hi angweav...

I viewed your page/sourcecode (Netscape7... with no problems) and I notice that the following section appears to be causing the problem:
<script language="JavaScript" fptype="dynamicoutline">
<!--
function dynOutline() {}
//-->
</script>
<!-- hide from older browser<BR><script language="JavaScript1.2" fptype="dynamicoutline" src="outline.js">
</script>
<script language="JavaScript1.2" fptype="dynamicoutline" for="document" event="onreadystatechange()">
</script>//-->

It just doesn't seem to have any purpose (other than throwing errors :eek: lol)..

Try taking that out and making sure that everything runs without it (it should).

By the way... I really like your menu links (esp the colors)!
I'm gonna swipe 'em :eek: :rolleyes: lol

;) k

I tried removing all of the above code and MS Frontpage put it right back in. So I removed the line about "outline.js" and it let me save it. I also decided to go look in my folder to see what all was saved in it and I found an outline.js file so I uploaded it to the server. However, this still did not fix the problem because I just called my partner and she said it locked up her browser at 19%.

Any ideas?

[khaki]

all good info from Gil (as always ;) )...
but i guess that my actual point was:

in the absence of a file named "outline.js"...
there would be no purpose in forcing the page to process those lines.
right :confused:

anyway... i don't understand why (or how) FP would re-write anything that was removed from the page. something is not right there.

ultimately... if you like the page as-is (and it looks good in my browsers).... why include scripts which do not seem to do anything except throw errors (those scripts don't seem vital to the page... although i am not testing with N4.7).

if you need it... keep it.
if you don't need it... kill it.

jacked-up and overdosing on jelly-beans...
;) k

[angweav]

Thank you so much for your help. Unfortunately I was unable to figure the problem out so I ended up redoing the site and leaving the javascript off.

If you care to take a peek, the finished page is here:

http://www.rootsweb.com/~txpanola

and the page with javascript is here:

http://www.rootsweb.com/~txpanola/index1.htm

Thanks again.

Angela
Panola County TXGenWeb Co-Coordinator