Alignment Issues in Firefox and Mac IE 5

Poster: Samuel
Dated: Wednesday April 28 2004 - 5:14:27 BST

Hi, I have the menu's setup perfectly in Netscape 4.8 and IE 6, however in FireFox the dropdowns extend too far and on the mac, the alignment of the menu itself is not correct. You can see this here:

http://www.basetwo.co.nz/beta/urbus/default.htm

and on the subpages:

http://www.basetwo.co.nz/beta/urbus/pro ... ault.shtml

Thanks, Sam.

Poster: Maz
Dated: Wednesday April 28 2004 - 6:11:17 BST

I'm not familiar with buttonover.

Place the menu scripts under the body tag with milonic_src.js first.

I'm not sure if I understand all of it.

maz

Poster: Samuel
Dated: Wednesday April 28 2004 - 23:41:06 BST

Umm, anybody else? The menu itself is working it's just not working right on Firefox.. we've used this script on other sites and I'm happy to register for this one if you can fix it on the mac and on firefox.

Come on guys, what's going wrong with it?

(I tried shifting the src file to under the body on one of the pages, no difference..)

Poster: Maz
Dated: Thursday April 29 2004 - 3:59:41 BST

First let's clean it up.

/*subimage="arrow.gif";*/
/*subimagepadding="2";*/
/*overfilter="Fade(duration=0.2);Alpha(opacity=100);Shadow(color='#777777', Direction=135, Strength=5)";*/

Take these out, anything you are not using should be removed. Some browsers are more finikey than others.

remove the gap, you might get a hidden character in there.

screenposition="center";

top=160;

where you have a single character
padding="5";
remove the quotes.

You can place the menu_data.js script in the table but not the others, all the scripts must go under the body tag.

maz

Poster: John
Dated: Thursday April 29 2004 - 15:22:24 BST

I have to tell you (and this goes for others reporting Firefox problems as well), reporting problems in a beta-version browser, and spending your own time trying to make things work in it, is, IMHO, a waste of effort.

From the Firefox home page...

As I'm sure you realize, beta software is in a constant state of change. Something we might fix today could well be broken tomorrow because of an upgrade.

With all due respect, I'd really suggest waiting for their final version before spending your resources (and ours) on it.