A. HTML and CSS-P-based content cannot overlap across frameset borders -- just as images can't. See the "Menus in Frames" section in the article at the following URL:

http://developer.netscape.com/viewsource/smith_menu2/menu.html

A. HTML and CSS-P-based content cannot overlap across any native OS-based components, such as: framesets, applets, or even standard Form input elements. This is a web browser limitation that you'll need to work-around, e.g. by either re-arranging your content so that the menus don't overlap across the area, or by wrapping the native components inside an CSS-P element and then hiding that element when the menu is displayed.

A. IE 4 has a problem with the document background color; so, you'll need to call the function that loads the menus somewhere after the Body tag (preferably at the end of the page source). See the following page source for an example of doing this:

http://developer.netscape.com/docs/examples/javascript/menu/iefixes.html

A. IE 5 doesn't allow DHTML to be created before the html BODY tag. My original menu article has the menu creation script being called inside the HEAD tags (as where scripts should be). However, due to this IE 5 layout problem, you now have to call a function that loads your menus somewhere after the BODY tag. See the Simple Menu page for an example of how to do this.