W
Wally S
I have read stuff here and on the internet about the benefits of laying out
with CSS instead of tables, so I decided to try it out. I copied one of my
pages laid out with tables and created an identical page using CSS. It was
easy because it was a simple two-column layout.
But what's the advantage? The estimated loading time on the bottom of the
screen is exactly the same for both versions. The CSS isn't any easier or
faster to work with, and you have to be careful about long, unbreakable
words. If you have one, and the reader enlarges the font, the right-hand
column will go crashing to the bottom of the page.
With tables, you might get something ugly and mashed-up, but it won't
destroy your layout. It took me quite a while to find the long, unbreakable
word because the right-hand column had gone down to the bottom, whereas with
a table I could have spotted it right away. I couldn't find any fix for this
on the web.
So I found a disadvantage but no advantage. Am I missing something?
Wally S
with CSS instead of tables, so I decided to try it out. I copied one of my
pages laid out with tables and created an identical page using CSS. It was
easy because it was a simple two-column layout.
But what's the advantage? The estimated loading time on the bottom of the
screen is exactly the same for both versions. The CSS isn't any easier or
faster to work with, and you have to be careful about long, unbreakable
words. If you have one, and the reader enlarges the font, the right-hand
column will go crashing to the bottom of the page.
With tables, you might get something ugly and mashed-up, but it won't
destroy your layout. It took me quite a while to find the long, unbreakable
word because the right-hand column had gone down to the bottom, whereas with
a table I could have spotted it right away. I couldn't find any fix for this
on the web.
So I found a disadvantage but no advantage. Am I missing something?
Wally S