Cascading Style Sheets, level 1
W3C Recommendation 17 Dec 1996, revised 11 Apr 2008
Tables should not be used purely as a means to layout document content as this may present problems when rendering to non-visual media. Additionally, when used with graphics, these tables may force users to scroll horizontally to view a table designed on a system with a larger display. To minimize these problems, authors should use style sheets to control layout rather than tables.
i.e. Your table design will break the user's browser
Ok, so beyond the specification thing here's the problem I see,
You guys that use WYSWYG editors and/or tables who don't want to learn CSS keep nesting tables to force
the browser to do what you want it do.
This adds to the overall web page file size where the file size could be better used to add important stuff like content!
Tables "stall" the rendering of a page because the browser has to read all your table coding to figure out how to create the table(s) you built. News flash: not everyone has the latest greatest computer or web connection.
And even if the visitors do have newer stuff, depending on how many tables you used, what's running on their computer at the same time and how fast their connection is at the specific moment they visited your site your page can still hesitate when rendering. Oh, there's the server load too that can effect delivery of your web pages whether you use tables or not. Anything you can do to improve the rendering of your pages is a good thing.
Here, Learn to Design HTML Tables with Less Code
, I show readers condensing your table coding using colspan and rowspan alone in the simple example saved 10% on that table. Now think about all the nested tables people use plus inline cell formatting (which most has been deprecated since HTML 4.01). That not only is a lot of coding to maintain it takes away from the content "space" available on a good file size for a web page.
Dispite the fact the WYSWYG editors and other programs let you create web pages, the web is not print
! You have no control over the visitor's machine, their settings, their connection, etc. (Well, you might find programming to force the issue and end up making the visitor leave in disgust 'cause you screwed with their settings