Member Rara Avis
Please feel free to poke this full of holes, as it was as much to learn as it was for the possibility of a working idea.
I have the DHTML menu shown from the other topic in here at http://countlesshorizons.com/newdesign/ I have it working now in both IE and Netscape v4+ (after doing what Ron suggested and tearing it down to nothing and rebuilding - it was a table issue).
The idea: Set it up so that if the user doesn't have scripting capabilities - or has it turned off - they will have a static menu in place of the DHTML one. To do this (and pardon me if it's really clumsy and messy - I'll rewrite everything once it's figured out) I used a js include ( http://countlesshorizons.com/newdesign/menu.js ) to write the DHTML menu into the body as the page is loading. Reasoning was that if they don't have scripting capabilities, nothing will be included. In that case, using <noscript> w/o HTML comment tags, the browser would write in the static menu.
I've done this now http://countlesshorizons.com/newdesign/testing.htm and tested it in IE and Netscape which both show it properly.
Concern: The scripting potion I'm fairly confident in. If they don't have it - it won't write in the DHTML. If they do, it will. No harm, no foul. If they don't have css capability or scripting ability - again, no harm. HOWEVER (and I don't know the likelihood of this) if they DO have scripting, but don't have css... ouch. Then what happens is that the script is written, but the browser is unable to use the layers - placing the 'dhtml' menu (which is no longer dynamic w/o the css) on the top of the screen over the background image. YUCK. If this ends up being a tenable route to travel - is there a way to use JS to check for css support? If so, I could include that in the funtion of whether or not to run the script.