Weird LI problem in FireFox

[indexhead]

I have a strange FF problem which I have been trying to solve for days. It involves the absolute positioning of a an outer list DIV element containing several inner list DIV elements.

The list is absolutely positioned and is in the correct spot in IE and FF. The problem is that even though the list is positioned correctly on the page in FF, the individual LI elements are offset to the right by 40px.

I have validated the XHTML, validated the CSS, double-checked the DOCTYPE, twiddled with every margin, padding, float etc. trick I can think of and nothing seems to solve the problem so that the LI elements are correct in both IE and FF.

Take a look at http://www.bluemagoo.com/bikefirst/bikehatsu.html

The CSS is all embedded, so no external SS to look at.

Thanks,

[Fang]

ul {padding:0;}

[drhowarddrfine]

Yep. As always, FF should be your reference for how things should work. NEVER IE!

[indexhead]

ul {padding:0;}

Thanks! That worked great.

[indexhead]

Yep. As always, FF should be your reference for how things should work. NEVER IE!

Excellent resources. BrowserWatch etc. still has FF @ 17.2% of all users, so IE still in the mix!

[newseed]

Excellent resources. BrowserWatch etc. still has FF @ 17.2% of all users, so IE still in the mix!

The point is that you should code for FF and not IE. FF displays what you've coded and so if you mess up or something is off, FF will show it. On the other hand, IE is not quite standard compliant yet and so it tends to displays incorrectly at times depending the CSS used (padding, border, etc.)

So code for FF and then if it's messed up in IE, used IE Conditional Comments (CC). 9 times out of 10 you will not have to use IE CC when properly coded.

[Kor]

Excellent resources. BrowserWatch etc. still has FF @ 17.2% of all users, so IE still in the mix!

check for IE6, not for all the IE browsers, because IE6 is the black sheep of the family: it has an incomplete standard CSS implementation and it has also numerous CSS bugs. Now, you will see that IE6 is not on rule at all.