It is important that the AllWebMenus HTML menu-linking section is placed immediately before the </BODY> tag and not somewhere else. This allows for the floating menus to appear properly on the page without being dismantled by other page elements (such as tables etc.), mostly in Netscape browsers.
How it works:
When inserting a menu into a web page, something similar to the following code is added just before the </BODY> tag:
<!-- ******** BEGIN AllWebMenus CODE FOR menu ******** -->
<img name='awmMenuPathImg-menu' id='awmMenuPathImg-menu' src='./awmmenupath.gif' alt=''>
<script type='text/javascript'>var MenuLinkedBy='AllWebMenus [2]', awmBN='482'; awmAltUrl='';</script>
<script src='menu.js' language='JavaScript1.2' type='text/javascript'></script>
<script type='text/javascript'>awmBuildMenu();</script>
<!-- ******** END AllWebMenus CODE FOR menu ******** -->
This HTML section should always remain there no matter where you want the menu to appear. Why?
Since the menu floats on the page, its appearing position is not determined by where you place the AllWebMenus HTML menu-linking section but by the <Vertical Distance from Edge> and <Horizontal Distance from Edge> properties. Therefore, it does matter that you do not move the HTML Section from the end of the page!
What about Includes, Libraries, Templates, etc.? The same rule applies to includes, libraries and templates. If you want to have a menu into a library or an include then you should make sure that:
1. the menu is always at the very end of the library or include and
2. the library or include is the last element of the page, just before the </body> tag.
If both conditions are satisfied, the resulting page will have the AllWebMenus HTML section at the very end of the page and no problems in Netscape will occur.
What about FrontPage Shared Borders?
A similar logic applies to the use of FrontPage Shared Borders.
This topic is best described in the "Compile Properties, FrontPage Support" section.