also having problems in firefox (mac)

Poster: designer
Dated: Friday October 13 2006 - 6:00:31 BST

http://bayfrontestatesatmillbasin.com/test/

It is very sluggish and the drop downs backgrounds are white (they are supposed to be black), and the blue "on" background stays as if it is a visited link.

I used the same settings on another isp and they work fine; could the host (ipowerweb) have settings that mess up the functionality in FF? I tested in Safari and it works the way it is intended to.

I'm not sure if ipowerweb is a linux or windows server... would that make a difference?

Thanks.

Poster: Ruth
Dated: Friday October 13 2006 - 8:28:52 BST

Hi,

You have a hash mark listed in places where you're using the word 'black to define a color. That's causing the submenu problem. Don't know why it's not doing that in the main menu.

Also, it seems to work, [although I only tested in FF and IE] but there are two methods for putting the menu in a div/table and you are not using either.

1. put all the calls for all the files in the div and place _buildAfterLoad=true; up in the global properties in the bfe_main_menu.js. Global properties are the area that has subOffsetTop etc.

2. Cut the main menu from your data file, put it in its own file and call only that file in the div, while calling the other files immediately the first thing after the body tag.

Ruth

Poster: designer
Dated: Friday October 13 2006 - 16:36:20 BST

First, the hash mark removal solved the problem, thank you!

Second, I don't understand what is different between the way I am presenting the menu and the second option you wrote about. I simply renamed the main file... is there another thing I'm doing differently?

By the way, the files immediately under the body tag are in the header include, not on each page... if that is what is different.

Thanks

Poster: Ruth
Dated: Saturday October 14 2006 - 21:51:14 BST

Hi,

The second method as described has something to do with having the program files and the submenus built before anything else on the page including the main menu.

When using that you are supposed to put the main menu into its own file, and you include a drawMenus(); at the end of it. This file then goes into the table, while the program files and the file with the styles, submenus etc go right after the body tag, being called right after the body tag they get built before anything else on the page. I am not a programmer so I don't know why but those are the directions from Milonic.

http://www.milonic.com/tablemenu.php

Ruth

Poster: designer
Dated: Saturday October 14 2006 - 23:11:13 BST

That method seems rather convoluted... my method did the same thing, but placed everything in the 'include' file, so that if I wanted to use a different nav system in the future I would just create a new header include and not have any extraneous js language in any of the pages.

... I think

Poster: Ruth
Dated: Sunday October 15 2006 - 13:35:43 BST

Hi,

I think that is the reason for the new method of putting all the files into the cell and using the new property of buildAfterLoad=true; From that property I am deducing that it is necessary that the main menu is not built without the submenus being built at the same time and that something to do with how tables are rendered and objects are built as the page loads is involved.

As to your method of putting the whole data file in the table, as I said it seems to work correctly, but I only have a pc with FF and IE so I have no idea what happens in other browsers or other platforms.

Ruth