mercurius_1@yahoo.com wrote:
[color=blue]
>Thanks for the response, I may have to go that route. But I was really
>hoping to avoid the old HTML table crutch. I wanted to achieve this
>layout more with CSS....Any additional ideas?[/color]
Sure, but since your clients don't care, you being css challenged, and
time/money being an issue, why would you want to? Given the content &
layout, using a table for layout is unlikely to cause problems for users
of the site.
The 3 main methods (floats, abs positioning, and IE bugs) available to
get IE to play ball are fraught with potential issues that sometimes lie
hidden just beneath the surface. Getting css layouts to work in IE
requires finely tuned css skills, without that people often do more
damage to the quality than they are aware of.
The page at the url you posted is simple enough for us to convert into a
css layout, but without the underlying knowledge, using it would likely
result in a site that causes more problems for users than a html table
layout would.
If you, in the spirit of new year resolutions, feel the need to move
away from "crutches", I suggest tackling the other issues I alluded to,
those, unlike a table hack are much more likely to cause problems for
users.
I'd suggest tackling these issues:
1) Text zooming breaks the layout (use the em unit to size the width of
the left box containing the navigation).
2) The stacking problem in Opera I mentioned.
3) Marking up the nav links as a unordered list.
4) Changing the charset specified via the meta element to something more
friendly (currently a Windows char set).
5) Removing the presentational bits from the html and switch to a Strict
doctype.
6) Remove those awful <p> </p> contraptions and switch to css
margins and padding.
7) The current layout blank space specified using the px unit doesn't
scale to different viewport sizes, using % as the unit would help
considerably.
--
Spartanicus