> I know using multiple tables, nested "n" levels deep is > stupid and results > in lots of excess code. So is using font tags etc. That's > why I don't > design that way. But sometimes it is (to me) unavoidable to > use a table, > because the alternatives just don't work consistently enough across > browsers.
This is the approach recommended for people getting started with css layouts in Zeldman's most excellent tome, "Designing with web standards". I think it's a good approach... I usually go for a fully css-positioned layout first, but sometimes extenuating (sp?) circumstances force us to use a table. For example, just last week we had a lovely three column layout, but unfortunately Macromedia Contribute wouldn't allow one of the columns to be edited, so we had to change the floated columns to a single three column table. It's not ideal, but not exactly the end of the world either. K. -- Kay Smoljak http://kay.smoljak.com ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
