Oh, and sorry for not including this in my other email, but upon looking
over the code quickly, I just want to throw this in:
Non-table design does not work exactly like table based design. For
example, that top graphic was three slices in a table, but in CSS, it
can be a single image.
That top row of buttons really ought to be in a list. It doesn't HAVE
to be (what you have works), but semantically it probably would work
better as a list.
That note above also goes for the links along the left. Quick rule of
thumb: only use a <div> or a <span> if nothing else seems to logically
fit. The left structure is more a list of links, so it could go in a
list as well.
In fact, I would just basically toss all the Imageready code entirely
and try marking it up from scratch. It seems like an insane route to
go, but Imageready is treating it as if it were a table-based layout.
The sheer number of <div>'s with {position: relative; float: left}
suggests that it would be much better just to go div {position:
relative; float: left} and override it for <div>'s that don't need it.
--
http://www.mozilla.org/products/firefox/ - Get Firefox!
http://www.mozilla.org/products/thunderbird/ - Reclaim Your Inbox!
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
