I recall the greatest need to rely on tables for predictable form layout was the disparity between browser CSS handling. Though still not perfect, I agree that using CSS reliably for almost any form layout is much easier now that several older browsers have fallen by the wayside (IE 5.x, Netscape < 6). It takes awhile to find or establish some best practices, but once you do it's tough to justify using tables for anything.
In reviewing a recent design with my developer, we were walking through the site and came across the only page with a table, displaying sortable columns of data, and actually had to pause to say: "And I had to use a table here because...well...it's a table...". 4 years ago, it would have been the opposite... Bryan http://www.bryanminihan.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Harrelson Sent: Tuesday, January 22, 2008 12:37 PM To: [email protected] Subject: Re: [IxDA Discuss] Liquid Blueprint While it may _seem_ easier on first blush to layout a form with tables (e.g. labels in left column, fields in right) it's usually less code to layout the same form with CSS and pretty easy once you do it a couple of times. ...Dan ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
