Putting non-windowed elements (like HTML-menus) on top of a frameset

[molendijk]

1) CODE TITLE:
Putting non-windowed elements (like HTML-menus) on top of a frameset (or: a technique for having non-evil framesets)

2) AUTHOR NAME: Arie Molendijk

3) DESCRIPTION:
The scripts, styles and techniques explained here ensure that:
* you can have anything you want on top of the frames of a frameset, which is a possibility we use here for having normal 'non-frameset menus' in a frameset environment;
* you'll always have the 'correct URL' in the addressbar, so bookmarking specific pages belonging to the frameset doesn't pose problems (anymore);
* search engines won't have particular problems in finding the specific pages of the frameset, since having the correct URL in the addressbar helps the engines to find them ('inurl').

But why would we want framesets at all? Well, the technique explained here offers some sort of alternative for people who cannot use SSI (server-side include) for cases in which CSI (client-side include) might not work. And, in general, client-side includes don't allow us to insert 'foreign' content; frames do.

4) URLS TO CODE:
http://molendijk.110mb.com/include_m..._on_top_smooth
http://molendijk.110mb.com/include_m...top_twinhelix/
http://molendijk.110mb.com/include_m..._top_ddlevels/

[molendijk]

Febr. 12:
I made a couple of minor changes / corrections. In the explanatory text, I made clear(er) that this technique of using framesets makes framed documents behave like ordinary ones. And it allows us to do more than standard client-side includes.
===
Arie.

[molendijk]

Here is a tutorial about dynamically passing data from one HTML-page to the other.
The tutorial is directly related to this thread.
===
Arie.