<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: CSS and Tables; The war continues</title>
	<atom:link href="http://ajaxian.com/archives/css-and-tables-the-war-continues/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/css-and-tables-the-war-continues</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: traza</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-278281</link>
		<dc:creator>traza</dc:creator>
		<pubDate>Wed, 27 Jan 2010 18:54:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-278281</guid>
		<description>The one that continues using tables is because it does not dominate or does not know CSS. To design in CSS is far better, by the subject of order, maintenance, accessibility, navigability and thousand reasons more.</description>
		<content:encoded><![CDATA[<p>The one that continues using tables is because it does not dominate or does not know CSS. To design in CSS is far better, by the subject of order, maintenance, accessibility, navigability and thousand reasons more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miscon2</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-269174</link>
		<dc:creator>miscon2</dc:creator>
		<pubDate>Tue, 18 Nov 2008 16:01:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269174</guid>
		<description>When building enterprise level sites, the amount of markup in a page matters.  The extra amount of code in a complex table-based layout may seem trivial, but multiply it by a million hits a month and it does have impact.

An example I recently ran into -&gt; loading paginated comments via ajax with a CakePHP MVC backend.  The view (HTML template) for each comment was built using tables.  The site could easily produce 300-500 comments per page.  Mix ajax loads with PHP application of a chunky DOM structure and we were getting long wait times before a given page of comments would appear.

Solution: reduce HTML per comment via the use of few block-level tags styled via CSS.   Problem solved.

I&#039;m NOT saying tables don&#039;t have their place, but I would argue that when we do need to use them its typically because we have to support old browsers that don&#039;t handle CSS well.  In other words, its crappy old browsers that will someday die that put us in the corner - not CSS.</description>
		<content:encoded><![CDATA[<p>When building enterprise level sites, the amount of markup in a page matters.  The extra amount of code in a complex table-based layout may seem trivial, but multiply it by a million hits a month and it does have impact.</p>
<p>An example I recently ran into -&gt; loading paginated comments via ajax with a CakePHP MVC backend.  The view (HTML template) for each comment was built using tables.  The site could easily produce 300-500 comments per page.  Mix ajax loads with PHP application of a chunky DOM structure and we were getting long wait times before a given page of comments would appear.</p>
<p>Solution: reduce HTML per comment via the use of few block-level tags styled via CSS.   Problem solved.</p>
<p>I&#8217;m NOT saying tables don&#8217;t have their place, but I would argue that when we do need to use them its typically because we have to support old browsers that don&#8217;t handle CSS well.  In other words, its crappy old browsers that will someday die that put us in the corner &#8211; not CSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: garann</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-269134</link>
		<dc:creator>garann</dc:creator>
		<pubDate>Mon, 17 Nov 2008 17:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269134</guid>
		<description>@ThomasHansen, I have examples of a few &lt;a href=&quot;http://garann.wordpress.com/2008/10/08/forms-without-lists/&quot; rel=&quot;nofollow&quot;&gt;tableless forms here&lt;/a&gt;. I don&#039;t know if I&#039;d go so far as to call them beautiful, but they work in modern browsers and offer decent layout options.</description>
		<content:encoded><![CDATA[<p>@ThomasHansen, I have examples of a few <a href="http://garann.wordpress.com/2008/10/08/forms-without-lists/" rel="nofollow">tableless forms here</a>. I don&#8217;t know if I&#8217;d go so far as to call them beautiful, but they work in modern browsers and offer decent layout options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ThomasHansen</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-269125</link>
		<dc:creator>ThomasHansen</dc:creator>
		<pubDate>Mon, 17 Nov 2008 10:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269125</guid>
		<description>@TheWorld
I can do mostly any layout my heart desires without having to resort to tables, but there is one place I get stuck still - forms...
Does anyone here have a beautiful recipe for how to create CRUD forms using CSS and getting the alignment right...?
I have tried a couple of times but I always end up with tables...</description>
		<content:encoded><![CDATA[<p>@TheWorld<br />
I can do mostly any layout my heart desires without having to resort to tables, but there is one place I get stuck still &#8211; forms&#8230;<br />
Does anyone here have a beautiful recipe for how to create CRUD forms using CSS and getting the alignment right&#8230;?<br />
I have tried a couple of times but I always end up with tables&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ypctx</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-269119</link>
		<dc:creator>ypctx</dc:creator>
		<pubDate>Sun, 16 Nov 2008 15:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269119</guid>
		<description>DiSiLLUSiON has summed it up nicely, why TABLES simply cannot die yet. Any alternative mentioned (XUL, Flash, whatnot) may be better option than a non-working CSS, but it is much worse option than having a working TABLES.
The thing is - when I begin to implement a design that smells with complexity, I never know in advance whether I will hit the CSS problems DiSiLLUSiON has mentioned - the requirements simply change too fast - and the world is just too interesting place to spend all time with needless refactoring. Therefore I play it safe and use tables from the get go, which I&#039;m very proficient at both from HTML as well as DOM side.
(Someone here said that &quot;floats kill kittens&quot;, so let me just add that TD rowspan kills puppies - both are things to avoid.)
Attempting to produce a clean work with messy and broken tools (current web starndards and their implementation by browsers) is simply foolish.
Once I can use CSS for everything where I use TABLE, but WITHOUT fugly hacks like conditinal CSS includes and deep nesting, I will be all CSS. Until then, I use both, as I&#039;m not their bitch to exploit, they are mine:)</description>
		<content:encoded><![CDATA[<p>DiSiLLUSiON has summed it up nicely, why TABLES simply cannot die yet. Any alternative mentioned (XUL, Flash, whatnot) may be better option than a non-working CSS, but it is much worse option than having a working TABLES.<br />
The thing is &#8211; when I begin to implement a design that smells with complexity, I never know in advance whether I will hit the CSS problems DiSiLLUSiON has mentioned &#8211; the requirements simply change too fast &#8211; and the world is just too interesting place to spend all time with needless refactoring. Therefore I play it safe and use tables from the get go, which I&#8217;m very proficient at both from HTML as well as DOM side.<br />
(Someone here said that &#8220;floats kill kittens&#8221;, so let me just add that TD rowspan kills puppies &#8211; both are things to avoid.)<br />
Attempting to produce a clean work with messy and broken tools (current web starndards and their implementation by browsers) is simply foolish.<br />
Once I can use CSS for everything where I use TABLE, but WITHOUT fugly hacks like conditinal CSS includes and deep nesting, I will be all CSS. Until then, I use both, as I&#8217;m not their bitch to exploit, they are mine:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: luke01</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-269115</link>
		<dc:creator>luke01</dc:creator>
		<pubDate>Sun, 16 Nov 2008 03:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269115</guid>
		<description>Fine post, &lt;em&gt;ajaxian&lt;/em&gt;, but I think you just started another flame war.</description>
		<content:encoded><![CDATA[<p>Fine post, <em>ajaxian</em>, but I think you just started another flame war.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PeterMichaux</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-269113</link>
		<dc:creator>PeterMichaux</dc:creator>
		<pubDate>Sun, 16 Nov 2008 00:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269113</guid>
		<description>Thanks for this one! :-D</description>
		<content:encoded><![CDATA[<p>Thanks for this one! :-D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TNO</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-2#comment-269106</link>
		<dc:creator>TNO</dc:creator>
		<pubDate>Fri, 14 Nov 2008 16:25:58 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269106</guid>
		<description>Oh yes, and something that isn&#039;t controlled by a single vendor and doesn&#039;t require a download for the user.</description>
		<content:encoded><![CDATA[<p>Oh yes, and something that isn&#8217;t controlled by a single vendor and doesn&#8217;t require a download for the user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TNO</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269105</link>
		<dc:creator>TNO</dc:creator>
		<pubDate>Fri, 14 Nov 2008 16:21:47 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269105</guid>
		<description>@endOfLine:
Something that doesn&#039;t cost a bajillion dollars to develop for,
doesn&#039;t require a leaky abstraction in the page,
 is easy to index by a search engine, 
can be quickly updated without firing up an IDE, 
Is  standardized and future compatible
Is readable
Is open source</description>
		<content:encoded><![CDATA[<p>@endOfLine:<br />
Something that doesn&#8217;t cost a bajillion dollars to develop for,<br />
doesn&#8217;t require a leaky abstraction in the page,<br />
 is easy to index by a search engine,<br />
can be quickly updated without firing up an IDE,<br />
Is  standardized and future compatible<br />
Is readable<br />
Is open source</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: endOfLine</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269103</link>
		<dc:creator>endOfLine</dc:creator>
		<pubDate>Fri, 14 Nov 2008 15:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269103</guid>
		<description>use Flex. It looks the same in every browser, provides as complicated a layout as you want, and gives you selectable text! What more could you ask for?</description>
		<content:encoded><![CDATA[<p>use Flex. It looks the same in every browser, provides as complicated a layout as you want, and gives you selectable text! What more could you ask for?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TNO</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269067</link>
		<dc:creator>TNO</dc:creator>
		<pubDate>Thu, 13 Nov 2008 14:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269067</guid>
		<description>If you&#039;re referring to block elements not being allowed within inline elements, its trivial to replace it using first-line:
&lt;code&gt;
li:first-line{
	font-weight:bold;
	color:blue;
	line-height:2em;
	text-decoration:underline;
}
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>If you&#8217;re referring to block elements not being allowed within inline elements, its trivial to replace it using first-line:<br />
<code><br />
li:first-line{<br />
	font-weight:bold;<br />
	color:blue;<br />
	line-height:2em;<br />
	text-decoration:underline;<br />
}<br />
</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edeverett</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269065</link>
		<dc:creator>edeverett</dc:creator>
		<pubDate>Thu, 13 Nov 2008 13:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269065</guid>
		<description>@TNO - you can&#039;t be having troynt&#039;s H3s inside a span, but yes that would be simpler for my example.</description>
		<content:encoded><![CDATA[<p>@TNO &#8211; you can&#8217;t be having troynt&#8217;s H3s inside a span, but yes that would be simpler for my example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TNO</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269060</link>
		<dc:creator>TNO</dc:creator>
		<pubDate>Thu, 13 Nov 2008 13:03:04 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269060</guid>
		<description>instead of using  li use a span with inline block and it will work back to IE6 without a hack</description>
		<content:encoded><![CDATA[<p>instead of using  li use a span with inline block and it will work back to IE6 without a hack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edeverett</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269059</link>
		<dc:creator>edeverett</dc:creator>
		<pubDate>Thu, 13 Nov 2008 12:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269059</guid>
		<description>@troynt Here&#039;s the two minute version of that layout. &lt;a href=&quot;http://edeverett.co.uk/experiments/noTables.html&quot; rel=&quot;nofollow&quot;&gt;http://edeverett.co.uk/experiments/noTables.html&lt;/a&gt;. Ok, so there&#039;s a small hack for IE, but that&#039;s a small price to pay for the benefits of not using tables for layout (for me the benefits are most in having more maintainble flexible HTML).</description>
		<content:encoded><![CDATA[<p>@troynt Here&#8217;s the two minute version of that layout. <a href="http://edeverett.co.uk/experiments/noTables.html" rel="nofollow">http://edeverett.co.uk/experiments/noTables.html</a>. Ok, so there&#8217;s a small hack for IE, but that&#8217;s a small price to pay for the benefits of not using tables for layout (for me the benefits are most in having more maintainble flexible HTML).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edeverett</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269058</link>
		<dc:creator>edeverett</dc:creator>
		<pubDate>Thu, 13 Nov 2008 12:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269058</guid>
		<description>@troynt You should us a list then apply a style of inline-block to each li. Nice looking site though.</description>
		<content:encoded><![CDATA[<p>@troynt You should us a list then apply a style of inline-block to each li. Nice looking site though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tr0y</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269043</link>
		<dc:creator>Tr0y</dc:creator>
		<pubDate>Wed, 12 Nov 2008 23:38:27 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269043</guid>
		<description>grr.. ate my markup.

&lt;code&gt;



&lt;/code&gt;

Which looks like a table.

Should be a list
&lt;code&gt;





&lt;/code&gt;

If the LIs heights are not consistent this will break, you can fix this with javascript, but I want it to work without javascript as well.</description>
		<content:encoded><![CDATA[<p>grr.. ate my markup.</p>
<p><code></p>
<p></code></p>
<p>Which looks like a table.</p>
<p>Should be a list<br />
<code></p>
<p></code></p>
<p>If the LIs heights are not consistent this will break, you can fix this with javascript, but I want it to work without javascript as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tr0y</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269042</link>
		<dc:creator>Tr0y</dc:creator>
		<pubDate>Wed, 12 Nov 2008 23:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269042</guid>
		<description>@DiSiLLUSiON: wait, maybe your suggesting something that looks like...







Which looks a lot like...


That solution is no better than a table.

It should be a list


foo
bar
foo2

etc.</description>
		<content:encoded><![CDATA[<p>@DiSiLLUSiON: wait, maybe your suggesting something that looks like&#8230;</p>
<p>Which looks a lot like&#8230;</p>
<p>That solution is no better than a table.</p>
<p>It should be a list</p>
<p>foo<br />
bar<br />
foo2</p>
<p>etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tr0y</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269041</link>
		<dc:creator>Tr0y</dc:creator>
		<pubDate>Wed, 12 Nov 2008 23:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269041</guid>
		<description>@DiSiLLUSiON: Not so fast on that solution.
&quot;if a li was taller than the next, the row after would display only one li.&quot;

So your solution would require one to specify a height. I could use javascript to vjustify the elements, however I want it to work without javascript as well.</description>
		<content:encoded><![CDATA[<p>@DiSiLLUSiON: Not so fast on that solution.<br />
&#8220;if a li was taller than the next, the row after would display only one li.&#8221;</p>
<p>So your solution would require one to specify a height. I could use javascript to vjustify the elements, however I want it to work without javascript as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LeoHorie</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269039</link>
		<dc:creator>LeoHorie</dc:creator>
		<pubDate>Wed, 12 Nov 2008 21:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269039</guid>
		<description>One more thing I wrote a while back about tables that I think ties nicely with this discussion: &lt;a href=&quot;http://lhorie.blogspot.com/2008/09/using-tables-for-non-tabular-data-is-ok.html&quot; rel=&quot;nofollow&quot;&gt;using tables for non-tabular data&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>One more thing I wrote a while back about tables that I think ties nicely with this discussion: <a href="http://lhorie.blogspot.com/2008/09/using-tables-for-non-tabular-data-is-ok.html" rel="nofollow">using tables for non-tabular data</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WillPeavy</title>
		<link>http://ajaxian.com/archives/css-and-tables-the-war-continues/comment-page-1#comment-269037</link>
		<dc:creator>WillPeavy</dc:creator>
		<pubDate>Wed, 12 Nov 2008 21:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=5049#comment-269037</guid>
		<description>CSS really isn&#039;t that hard to learn. And once you do learn it - I believe it becomes much easier to maintain and alter large sites and apps than with a nested table layout.</description>
		<content:encoded><![CDATA[<p>CSS really isn&#8217;t that hard to learn. And once you do learn it &#8211; I believe it becomes much easier to maintain and alter large sites and apps than with a nested table layout.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

