<?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: Styleless</title>
	<atom:link href="http://andrewjaswa.com/2008/05/styleless/feed/" rel="self" type="application/rss+xml" />
	<link>http://andrewjaswa.com/2008/05/styleless/</link>
	<description>I build crappy websites every day!</description>
	<pubDate>Tue, 06 Jan 2009 06:03:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jon</title>
		<link>http://andrewjaswa.com/2008/05/styleless/comment-page-1/#comment-8</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 02 Jun 2008 19:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://andrewjaswa.com/?p=10#comment-8</guid>
		<description>Chris,

Since images are actually inline elements in xHTML, display:block makes them behave more as we'd expect... Most importantly, it gets rid of the 3px "gutter" at the bottom of images... inline space reserved for the descenders of letters q,y,j, etc.

I mostly use .floatleft / .floatright on IMGs my personal site.  I like to have a variety of image positions, i.e., not all floating on one side; some articles might start with an image on the left, others on the right. I'd love to  come up with a more semantic name for .floatleft / .floatright.  What would be better? .sideItemL / .sideItemR?  I suppose you could call them something like .image  and .illustration for purely semantic class names, but that adds a needless memory burden in the service of a purely idealistic goal, IMHO.  Your thoughts?</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Since images are actually inline elements in xHTML, display:block makes them behave more as we&#8217;d expect&#8230; Most importantly, it gets rid of the 3px &#8220;gutter&#8221; at the bottom of images&#8230; inline space reserved for the descenders of letters q,y,j, etc.</p>
<p>I mostly use .floatleft / .floatright on IMGs my personal site.  I like to have a variety of image positions, i.e., not all floating on one side; some articles might start with an image on the left, others on the right. I&#8217;d love to  come up with a more semantic name for .floatleft / .floatright.  What would be better? .sideItemL / .sideItemR?  I suppose you could call them something like .image  and .illustration for purely semantic class names, but that adds a needless memory burden in the service of a purely idealistic goal, IMHO.  Your thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Jones</title>
		<link>http://andrewjaswa.com/2008/05/styleless/comment-page-1/#comment-7</link>
		<dc:creator>Christopher Jones</dc:creator>
		<pubDate>Thu, 29 May 2008 20:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://andrewjaswa.com/?p=10#comment-7</guid>
		<description>Looks good to me. Out of pure personal preference and going by what I actually find myself doing, I would probably throw a boder:0 on fieldsets as well. No real reason, I just find that I end up turning them off more often than not.

JZ, two questions...
1. Why the display:block on all images?

2. Do you find that having a class name that explictly declares what it does hinders things? I have seen many people use various float classes, but to me it seems like the equivalent of having a class named 'red' instead of 'error'. It seems presentational instead of semantic.</description>
		<content:encoded><![CDATA[<p>Looks good to me. Out of pure personal preference and going by what I actually find myself doing, I would probably throw a boder:0 on fieldsets as well. No real reason, I just find that I end up turning them off more often than not.</p>
<p>JZ, two questions&#8230;<br />
1. Why the display:block on all images?</p>
<p>2. Do you find that having a class name that explictly declares what it does hinders things? I have seen many people use various float classes, but to me it seems like the equivalent of having a class named &#8216;red&#8217; instead of &#8216;error&#8217;. It seems presentational instead of semantic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Zuck</title>
		<link>http://andrewjaswa.com/2008/05/styleless/comment-page-1/#comment-6</link>
		<dc:creator>Jon Zuck</dc:creator>
		<pubDate>Sat, 24 May 2008 19:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://andrewjaswa.com/?p=10#comment-6</guid>
		<description>Oh, I almost forgot... a few other things I do on virtually every site: 
1. declare a float + opposite side margin for both directions, example:
floatleft: {float: left: margin-right: .5em;}
2. a img {border:0;}
3. img {display:block;}</description>
		<content:encoded><![CDATA[<p>Oh, I almost forgot&#8230; a few other things I do on virtually every site:<br />
1. declare a float + opposite side margin for both directions, example:<br />
floatleft: {float: left: margin-right: .5em;}<br />
2. a img {border:0;}<br />
3. img {display:block;}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Zuck</title>
		<link>http://andrewjaswa.com/2008/05/styleless/comment-page-1/#comment-5</link>
		<dc:creator>Jon Zuck</dc:creator>
		<pubDate>Sat, 24 May 2008 18:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://andrewjaswa.com/?p=10#comment-5</guid>
		<description>Nice baseline... Like Zach, I also like using border-collapse:collapse as a default.  And I think I'd separate the decimal list-type into a declaration for just ordered lists... 

I'd also probably declare a much-smaller line-height, possibly 1.25, for the headers, so bottom-spacing would sit headers nearer the content, and scale proportionately with the text size ... (interesting discussion about this in the the chapter on typography in Cascading Style Sheets, Briggs et al. about how larger type doesn't need the same line-heights as body type.) with a declared margin on the top alone.

Very nice job, Andrew</description>
		<content:encoded><![CDATA[<p>Nice baseline&#8230; Like Zach, I also like using border-collapse:collapse as a default.  And I think I&#8217;d separate the decimal list-type into a declaration for just ordered lists&#8230; </p>
<p>I&#8217;d also probably declare a much-smaller line-height, possibly 1.25, for the headers, so bottom-spacing would sit headers nearer the content, and scale proportionately with the text size &#8230; (interesting discussion about this in the the chapter on typography in Cascading Style Sheets, Briggs et al. about how larger type doesn&#8217;t need the same line-heights as body type.) with a declared margin on the top alone.</p>
<p>Very nice job, Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Young</title>
		<link>http://andrewjaswa.com/2008/05/styleless/comment-page-1/#comment-4</link>
		<dc:creator>Zach Young</dc:creator>
		<pubDate>Sat, 24 May 2008 17:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://andrewjaswa.com/?p=10#comment-4</guid>
		<description>Now that the CSS file is correct, looks pretty good. I think I would collapse the border on the tables. I'm assuming it works on Windows browsers (I don't have any of them here...) Nice work.</description>
		<content:encoded><![CDATA[<p>Now that the CSS file is correct, looks pretty good. I think I would collapse the border on the tables. I&#8217;m assuming it works on Windows browsers (I don&#8217;t have any of them here&#8230;) Nice work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.221 seconds -->
