Wednesday, February 4th, 2009
The basic gist is:
While CSS should be used for styling, tables should be used for layout.
The author lays out annoyances such as, CSS floats:
Apparently the order matters. The reason that the order matters is that this layout, like all multi-column CSS layouts, is achieved with floats, and the way that floats get rendered depends on the order in which they appear. So we have not managed to separate content from presentation. How things appear on the screen still depends on the order in which they appear in the content. Worse, in order to be rendered properly, the order in which elements must appear is different from their natural flow in the layout.
And then shows tables and how he prefers them.
CSS purist may poo poo him and say “he is just dumb and doesn’t REALLY know CSS.” The problem though is that most developers run into exactly the pain that he describes. We’ve all been there. It drives you nuts and when frustrated what do you do? You fluster about and change CSS like a mad man until it kinda looks right. And, you never learn what the real problem was, and thus destined to make the same mistake again.
We need something better for layout. And, maybe a touch more than ASCII art layout? ;)
NOTE: There are some amazing things about CSS for layout. The way you can deal with flow is actually quite interesting, so it aint all bad (it isn’t GridBagLayout!)
What do you think?
Posted by Dion Almaer at 7:36 am