Originally Posted by MeTaL_oRgY
The point for using DIVs instead of tables is semantic code. A table is for TABULAR data. A layout is not tabular data. A DIV is for grouping elements.
|
I know that tables are for tabular data. It's what they were originally used for. However, it's also a nice way of structuring things. HTML without tables is too simple on the other hand, although tables weren't used in the early days for website layouts.
Originally Posted by MeTaL_oRgY
And if you are trying to pretend that DIVs are tables when coding a CSS layout, you're doing it wrong. You don't need to pretend DIVs are tables, but blocks of elements. As you said, all the web elements have it's place; you just need to use them for the right things.
|
I didn't say anything about pretending that divs are tables. I said that you have to pretend that
there (not they're) are tables, but instead you're using divs and margins. This is for alignment, positioning, etc. In the same way as you can see content inside of a td tag on the left side or on the right side, you have to know the locations of where you're placing things. That's all I was saying.
Originally Posted by MeTaL_oRgY
And the whole reason for using CSS as much as you can instead of tables/javascript or anything else you can think of is mere accessibility. It loads faster, it's semantic and withouth CSS, chances are that it will still work.
|
Accessibility or quick loading isn't always what makes a good website though, but I understand what you're saying.
What, you don't want my bikini-clad body?