<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: On using tables for html layouts</title>
	<atom:link href="http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/feed/" rel="self" type="application/rss+xml" />
	<link>http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/</link>
	<description>escape colon w q</description>
	<pubDate>Sat, 22 Nov 2008 11:12:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Geekfindr: CSS Layouts &#124; #comments</title>
		<link>http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/#comment-769</link>
		<dc:creator>Geekfindr: CSS Layouts &#124; #comments</dc:creator>
		<pubDate>Sun, 01 Apr 2007 13:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/#comment-769</guid>
		<description>[...] in general I don&#8217;t love using CSS for the broad layout of a site. If the site is simple enough it makes sense and can really simplify [...]</description>
		<content:encoded><![CDATA[<p>[...] in general I don&#8217;t love using CSS for the broad layout of a site. If the site is simple enough it makes sense and can really simplify [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: felix</title>
		<link>http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/#comment-85</link>
		<dc:creator>felix</dc:creator>
		<pubDate>Fri, 02 Mar 2007 22:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/#comment-85</guid>
		<description>Yes, I really hope that CSS develops into something that really can do all it promises and more importantly I hope the browsers all start adhering to the same standard. To a large degree, I think that is the biggest culprit - if all the browsers supported the same CSS level in the same way, a lot of problems would go away and CSS hacks would not be compounded by stupid browser hacks. Sigh. Sadly, such a world does not look too likely in the foreseeable future.</description>
		<content:encoded><![CDATA[<p>Yes, I really hope that CSS develops into something that really can do all it promises and more importantly I hope the browsers all start adhering to the same standard. To a large degree, I think that is the biggest culprit - if all the browsers supported the same CSS level in the same way, a lot of problems would go away and CSS hacks would not be compounded by stupid browser hacks. Sigh. Sadly, such a world does not look too likely in the foreseeable future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/#comment-84</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Fri, 02 Mar 2007 21:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/03/02/on-using-tables-for-html-layouts/#comment-84</guid>
		<description>As an avowed CSS nerd, and a standards sympathizer, I say: yup, if you want equal-hight columns, you should use a table. 

The thing to keep in mind (and this is a major and very correct pillar of the standards movement) is that markup should be as semantic as possible. Using a border to contain content is easily as ridiculous as presenting the content as tabular data. There seems to be this notion out there that avoiding tables is worth any amount of smoke and mirrors.

Using a table for layout is, like you suggest, a hack. As with any CSS hack, use as few as possible, and keep them as simple as possible. (And avoid nested tables unless you want equal hight columns inside of other, larger, equal hight columns.)

Mostly, this all gets me thinking about layouts that don't depend on equal-height columns. That, and pining for future implementations of CSS...</description>
		<content:encoded><![CDATA[<p>As an avowed CSS nerd, and a standards sympathizer, I say: yup, if you want equal-hight columns, you should use a table. </p>
<p>The thing to keep in mind (and this is a major and very correct pillar of the standards movement) is that markup should be as semantic as possible. Using a border to contain content is easily as ridiculous as presenting the content as tabular data. There seems to be this notion out there that avoiding tables is worth any amount of smoke and mirrors.</p>
<p>Using a table for layout is, like you suggest, a hack. As with any CSS hack, use as few as possible, and keep them as simple as possible. (And avoid nested tables unless you want equal hight columns inside of other, larger, equal hight columns.)</p>
<p>Mostly, this all gets me thinking about layouts that don&#8217;t depend on equal-height columns. That, and pining for future implementations of CSS&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
