For those wondering, here are the good reasons why to avoid using tables and use CSS Positioning attributes and <div> tags:
1) Tables cannot be rendered properly until the entire block of code is loaded. This becomes a nasty issue when you use nested tables. While most browsers try to render realtime when buffering the download of a website, the proper display of a website cannot be obtained until the page has finished downloading.
2) While individual <div> blocks may have similar rendering issues, the don't require the entire thing to be loaded properly. Assuming one uses the CSS size and positioning attributes properly, each "cell" of a <div> can load, and be displayed immediately, and usually with proper respect to a website's design.
3) <div> provides much more control with regards to placement and sizing through the use of CSS. While tables are restricted to sizing, padding, and margin attributes. Tables can achieve a pseudo-positioning attribute when linked to CSS or are subsequently nested.
1) Tables cannot be rendered properly until the entire block of code is loaded. This becomes a nasty issue when you use nested tables. While most browsers try to render realtime when buffering the download of a website, the proper display of a website cannot be obtained until the page has finished downloading.
2) While individual <div> blocks may have similar rendering issues, the don't require the entire thing to be loaded properly. Assuming one uses the CSS size and positioning attributes properly, each "cell" of a <div> can load, and be displayed immediately, and usually with proper respect to a website's design.
3) <div> provides much more control with regards to placement and sizing through the use of CSS. While tables are restricted to sizing, padding, and margin attributes. Tables can achieve a pseudo-positioning attribute when linked to CSS or are subsequently nested.