Webforumz.com - View Single Post

saltedm8 · Mar 8th, 2008, 00:13

hows this for some very good reasons

I.Tables are usually more bytes of mark-up. (Longer to download, and more bytes of traffic for the host.)

II.Tables are usually slower to layout for the browser. (Takes longer for the user to see anything on the page.)

III.Tables usually prevent incremental rendering. (Takes longer for the user to see anything on the page.)

IV.Tables may require you to chop single, logical images into multiple ones. (This makes redesigns very hard, and also increases page load time [more http requests and more total bytes].)

V.Tables break text copying on some browsers. (That's annoying to the user.)

VI.Tables prevent certain layouts from working within them (like height:100% for child elements of <td>). (They limit what you can actually do in terms of layout.)

VII.Once you know CSS, table-based layouts usually take more time to implement. (A little effort up-front learning CSS pays off heavily in the end.)

VIII.Tables are semantically incorrect mark-up for layout. (They describe the presentation, not the content.)

IX.Tables make life hell for those using screen readers. (Not only do you get the other benefits of CSS, you're also helping out the blind/partially-sighted. This is a Good Thing.)

X.Tables lock you into the current design and make redesigns MUCH harder than semantic HTML+CSS.

Mar 8th, 2008, 00:13	#4 (permalink)
saltedm8 Lead Administrator Join Date: Nov 2005 Location: Always About Age: 27 Posts: 1,058 Blog Entries: 1	Re: I still love tables, but... hows this for some very good reasons I.Tables are usually more bytes of mark-up. (Longer to download, and more bytes of traffic for the host.) II.Tables are usually slower to layout for the browser. (Takes longer for the user to see anything on the page.) III.Tables usually prevent incremental rendering. (Takes longer for the user to see anything on the page.) IV.Tables may require you to chop single, logical images into multiple ones. (This makes redesigns very hard, and also increases page load time [more http requests and more total bytes].) V.Tables break text copying on some browsers. (That's annoying to the user.) VI.Tables prevent certain layouts from working within them (like height:100% for child elements of <td>). (They limit what you can actually do in terms of layout.) VII.Once you know CSS, table-based layouts usually take more time to implement. (A little effort up-front learning CSS pays off heavily in the end.) VIII.Tables are semantically incorrect mark-up for layout. (They describe the presentation, not the content.) IX.Tables make life hell for those using screen readers. (Not only do you get the other benefits of CSS, you're also helping out the blind/partially-sighted. This is a Good Thing.) X.Tables lock you into the current design and make redesigns MUCH harder than semantic HTML+CSS. __________________ recipebite.co.uk - its a working progress...