JavaScript Forum

**Skipjackrick** · 05:58 PM

This is the weirdest encounter I have ever had and frankly, I don't have a solution for it.

I am trying to make my pages w3 compliant since I haven't been doing so for a while I figured its about time I join the standards.

So, I started to make a layout document as my base. You can view it here.

http://www.extremecoast.com/KW09/layoutdoc2.php

Everything looks ok to start out..... Menu rollovers look good and flash is displaying properly... It passes w3 validation etc.

HOWEVER, when I visit my home page.

http://www.extremecoast.com

AND then return to my layoutdoc2.php my menu disappears!!! So I disabled javascript to see what was going on and the menu reappears. Or if I clear my browser history and it works again.

But when I visit the homepage my new layout is FRIED!

What is happening? What is javascript doing to my CSS? Can anybody help me?

**Sleeping Troll** · 02-13-2009, 06:08 AM

Can you provide some code?

**Skipjackrick** · 10:47 AM

Yes, The following code is my new layout document. That is at the following link.

However, I made a copy of my index page and named it javaruin.php and it doesn't pass anything to the browser which screws up my CSS.

The problem is only with my index file at the root from the host. Do you think the host could be passing something to the browser that is causing my problems?

I now know it has nothing to do with my code otherwise I would have observed the same problem from the javaruin.php file because it is an exact duplicate of my index page which causes the issues.

Code? For some reason the forum won't let me post big long lists?

This is my new layout document
http://www.extremecoast.com/KW09/layoutdoc2.txt

My Css file
http://www.extremecoast.com/KW09/layout/kayakwars.css

This is the code of the index page that I think is causing the issues.
http://www.extremecoast.com/KW09/index.txt

**Sleeping Troll** · 02-14-2009, 12:59 AM

If it is a "free" host they sometimes post an ad in place of an error page, this would produce some unexpected results.

I do see one thing that may or may not be a problem, in the switch statement, javascript will continue to test each case even after a "true" is found unless you insert a break after each case test.