usually gaps like that come down to Firefox being tolerant of non-ending tags or assuming that a height is set. IE is more litteral. Honestly, IE pisses me off.

 

there's nothing wrong with that. but just remember to check yourself before you go on preaching about best practices. there's really nothing more irritating to me in the web dev world than that.

 

Okay. Here is the site. This is still the rough draft so my code might be a little sloppy.

So I want more_col_nav-1.jpg on the right and nav_col_nav-1.jpg on the left. I can get one or the other but not both.

:flamesuiton:

 

Using a div tag will split them, but using a span tag won't.

 

here's a start. wrap the whole menu in a div w/ that purple color and you're good to go.

 

I'm not too keen on having a minimum width like that. Many of our users are using 640x400 or 800x600 resolutions and I want it to adjust for that as well as for larger resolutions.

 

set statements for those widths then....it will drastically help.

 

marshy site doesnt look bad.

w3 is tyring to promote divs because they found too many people know how to do html and they believe it is cutting into the market of people who's jobs are just html. (which if you know jsut html i dont see how you can get a job.) so now they are starting to make div's a standard practice to keep these people in jobs, cause it takes "div and css training" to complete.

what reno said is pretty accurate about pages being a mess, css files being over complicated. html was never suppossed to be over complicated, that is what made it great.

me? i stick with tables cause its easy. does .1-.6 extra second load time really matter anyways?

 

Well the span tags didn't work. I'm going to try playing around with the width and see if that might help.