<?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: Beginner&#8217;s Checklist Before Debugging CSS</title>
	<atom:link href="http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/</link>
	<description>Torrance Website Design - Soh Tanaka</description>
	<lastBuildDate>Mon, 22 Mar 2010 03:40:07 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: William</title>
		<link>http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/comment-page-1/#comment-2359</link>
		<dc:creator>William</dc:creator>
		<pubDate>Mon, 18 May 2009 00:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.sohtanaka.com/?p=1113#comment-2359</guid>
		<description>Here is another great tip.
The Order of the Rule.....

I find that defining the properties in the same order for every rule is a major help when debugging your style sheets.

It is a method I&#039;ve never seen on any other designers site style sheets (even your style sheet!)
It is a concept that I came up with a few years back after the frustration of debugging style sheet after style sheet.

Here is an example:
#ruleOne{margin: 0, width: 10px; height: 10px; padding: 0; background: #fff; color: #000;}
#ruleTwo{margin: 0, width: 20px; height: 20px; padding: 0; background: #000; color: #fff;}
#ruleThree{margin: 0, width: 30px; height: 30px; padding: 0; background: #00f; color: #f00;}
(Above are common properties in a simple order for the sake of the example.)

You can see what ever property that needs to be tweaked can be easily located within the rule.
The rules become far easier to read. And Math; one of the number one culprits to most css bugs is easy to spot and calculate. (it’s amazing how many browser discrepancies really boil down to properly calculating properties in the rules.)

What I commonly see in style sheets are a hodge-podge of properties that are slapped together as the designer needs to add the rule property.

It is common for rules to look like the following:

#ruleOne{background: #fff; width: 10px; padding: 0; height: 10px; margin: 0; color: #000;}
#ruleTwo{padding: 0; margin: 0; height: 20px; background: #000; width: 20px; color: #fff;}
#ruleThree{color: #f00; margin: 0, background: #00f; height: 30px; padding: 0; width: 30px; }

No rhyme or reason. Just a list of properties inserted into the rules as the designer find the need to insert them not realizing that it is later difficult to debug. 

Regards,
William</description>
		<content:encoded><![CDATA[<p>Here is another great tip.<br />
The Order of the Rule&#8230;..</p>
<p>I find that defining the properties in the same order for every rule is a major help when debugging your style sheets.</p>
<p>It is a method I&#8217;ve never seen on any other designers site style sheets (even your style sheet!)<br />
It is a concept that I came up with a few years back after the frustration of debugging style sheet after style sheet.</p>
<p>Here is an example:<br />
#ruleOne{margin: 0, width: 10px; height: 10px; padding: 0; background: #fff; color: #000;}<br />
#ruleTwo{margin: 0, width: 20px; height: 20px; padding: 0; background: #000; color: #fff;}<br />
#ruleThree{margin: 0, width: 30px; height: 30px; padding: 0; background: #00f; color: #f00;}<br />
(Above are common properties in a simple order for the sake of the example.)</p>
<p>You can see what ever property that needs to be tweaked can be easily located within the rule.<br />
The rules become far easier to read. And Math; one of the number one culprits to most css bugs is easy to spot and calculate. (it’s amazing how many browser discrepancies really boil down to properly calculating properties in the rules.)</p>
<p>What I commonly see in style sheets are a hodge-podge of properties that are slapped together as the designer needs to add the rule property.</p>
<p>It is common for rules to look like the following:</p>
<p>#ruleOne{background: #fff; width: 10px; padding: 0; height: 10px; margin: 0; color: #000;}<br />
#ruleTwo{padding: 0; margin: 0; height: 20px; background: #000; width: 20px; color: #fff;}<br />
#ruleThree{color: #f00; margin: 0, background: #00f; height: 30px; padding: 0; width: 30px; }</p>
<p>No rhyme or reason. Just a list of properties inserted into the rules as the designer find the need to insert them not realizing that it is later difficult to debug. </p>
<p>Regards,<br />
William</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hakan</title>
		<link>http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/comment-page-1/#comment-978</link>
		<dc:creator>hakan</dc:creator>
		<pubDate>Mon, 12 Jan 2009 18:39:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sohtanaka.com/?p=1113#comment-978</guid>
		<description>thanks</description>
		<content:encoded><![CDATA[<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doe</title>
		<link>http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/comment-page-1/#comment-641</link>
		<dc:creator>Doe</dc:creator>
		<pubDate>Fri, 12 Dec 2008 03:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sohtanaka.com/?p=1113#comment-641</guid>
		<description>Thank you very much for this list, I guess I&#039;m one of those people who make these really dumb mistakes X-p 

This should definately put me on the right track :-)</description>
		<content:encoded><![CDATA[<p>Thank you very much for this list, I guess I&#8217;m one of those people who make these really dumb mistakes X-p </p>
<p>This should definately put me on the right track <img src='http://www.sohtanaka.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Soh</title>
		<link>http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/comment-page-1/#comment-606</link>
		<dc:creator>Soh</dc:creator>
		<pubDate>Tue, 09 Dec 2008 16:06:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.sohtanaka.com/?p=1113#comment-606</guid>
		<description>ah yes, the almighty red border! I would definitely recommend that as well, but some beginners have a hard time figuring out where to look for problems (ex. the red border is not showing up, where to look now?), so these steps are in my opinion still a valid check list to go through.

Maybe red border first, then go back to the list :-)

Thanks Swizec!</description>
		<content:encoded><![CDATA[<p>ah yes, the almighty red border! I would definitely recommend that as well, but some beginners have a hard time figuring out where to look for problems (ex. the red border is not showing up, where to look now?), so these steps are in my opinion still a valid check list to go through.</p>
<p>Maybe red border first, then go back to the list <img src='http://www.sohtanaka.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Thanks Swizec!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hudson</title>
		<link>http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/comment-page-1/#comment-602</link>
		<dc:creator>Hudson</dc:creator>
		<pubDate>Tue, 09 Dec 2008 10:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.sohtanaka.com/?p=1113#comment-602</guid>
		<description>@ Swizec

Amen to the big red border method. Possibly the single most useful trick I know in CSS (believe it or not!). Saved me from many headaches.</description>
		<content:encoded><![CDATA[<p>@ Swizec</p>
<p>Amen to the big red border method. Possibly the single most useful trick I know in CSS (believe it or not!). Saved me from many headaches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Swizec</title>
		<link>http://www.sohtanaka.com/web-design/beginners-checklist-debugging-css-bug/comment-page-1/#comment-591</link>
		<dc:creator>Swizec</dc:creator>
		<pubDate>Mon, 08 Dec 2008 21:14:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.sohtanaka.com/?p=1113#comment-591</guid>
		<description>I find that the simplest way to check all those is to make an obvious change (personally I go for the nice red border) and if nothing obvious happens on the page you know you did something dumb instead of just a small mistake.

Learned the technique back in my Pascal days in the late 90&#039;s, always useful and all newbies should learn to cherrish it.</description>
		<content:encoded><![CDATA[<p>I find that the simplest way to check all those is to make an obvious change (personally I go for the nice red border) and if nothing obvious happens on the page you know you did something dumb instead of just a small mistake.</p>
<p>Learned the technique back in my Pascal days in the late 90&#8217;s, always useful and all newbies should learn to cherrish it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
