In your above case, this *ought* to work, since one of your frames is only navigation, and assuming that all you are doing on that frame is indicating where the user is on your site, this isn't a bad use. But most people that play with frames and JS this way don't have that constant navigation frame around, and instead are updating content in both frames at the same time; with JS off, only one frame gets updated, and the other stays where it was, possibly displaying different information and confusing the user.

Certainly, if we stick to the case above, that's not a problem, but now you've got to consider how you present the navigation area: do you have an arrow pointing to the current place? If the navigation is being updated, then to be effective when JS is turned off (and you cannot ignore this situation), you need to program separate operations for a JS enabled browser (so that the navigation dynamically updates) non-JS version (simply displaying the content). While checking for JS is simple, getting that to report back to you via CGI, and then having scripts that include or disclude JS can be a pain in the butt.

It's much easier, and much more usable by all browsers, JS or not, to regenerate the frame set if you want to update two or more frames at a time, or to switch to using tables for layout (something I'm not terribly fond of, but no doubt will work in nearly all browsers today).

---

Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain