<?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: Integrate Password Strength Checker into Registration Forms</title>
	<atom:link href="http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/</link>
	<description>- Hunting the Best Open Source Resources for Web Developers</description>
	<pubDate>Mon, 06 Oct 2008 15:55:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: toupil</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-10733</link>
		<dc:creator>toupil</dc:creator>
		<pubDate>Mon, 16 Jun 2008 13:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-10733</guid>
		<description>very good</description>
		<content:encoded><![CDATA[<p>very good</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Williams</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4389</link>
		<dc:creator>Ryan Williams</dc:creator>
		<pubDate>Thu, 20 Mar 2008 15:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4389</guid>
		<description>Easy clearing or my preferred method overflow: hidden; is good, but that's really for when there's nothing *after* those elements in that container. If you do have something after the floated elements like a block of text or something, you can simply apply the clearing to that.</description>
		<content:encoded><![CDATA[<p>Easy clearing or my preferred method overflow: hidden; is good, but that&#8217;s really for when there&#8217;s nothing *after* those elements in that container. If you do have something after the floated elements like a block of text or something, you can simply apply the clearing to that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spencer</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4387</link>
		<dc:creator>Spencer</dc:creator>
		<pubDate>Thu, 20 Mar 2008 14:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4387</guid>
		<description>oh ok, great.  Thanks for clearing that up.  The only reason I ask is because I've never seen it done that way before.  I've always used the Easy Clearing method documented at positioniseverything.net, or overflow:auto for the containing div.  But I am always looking for the easiest and best method for clearing floats.  Thanks for responding...

Spencer</description>
		<content:encoded><![CDATA[<p>oh ok, great.  Thanks for clearing that up.  The only reason I ask is because I&#8217;ve never seen it done that way before.  I&#8217;ve always used the Easy Clearing method documented at positioniseverything.net, or overflow:auto for the containing div.  But I am always looking for the easiest and best method for clearing floats.  Thanks for responding&#8230;</p>
<p>Spencer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Williams</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4384</link>
		<dc:creator>Ryan Williams</dc:creator>
		<pubDate>Thu, 20 Mar 2008 14:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4384</guid>
		<description>I find it hard to imagine how you'd produce a CSS-based site that works properly in all browsers *without* using width: 100% and clear: left; to be honest. Using clearing is an absolute must when floating elements (it stops them overlapping the content below), and using width: 100%; will throw Internet Explorer 6 into hasLayout mode which will fix some display weirdness with certain elements.</description>
		<content:encoded><![CDATA[<p>I find it hard to imagine how you&#8217;d produce a CSS-based site that works properly in all browsers *without* using width: 100% and clear: left; to be honest. Using clearing is an absolute must when floating elements (it stops them overlapping the content below), and using width: 100%; will throw Internet Explorer 6 into hasLayout mode which will fix some display weirdness with certain elements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spencer</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4369</link>
		<dc:creator>Spencer</dc:creator>
		<pubDate>Wed, 19 Mar 2008 23:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4369</guid>
		<description>Hello, I was just curious... I was looking at your source code, and seeing what technique you were using for your layout, specifically in regards to clearing floats.  I saw that you use in some of your containers width:100% and also clear:left.  Have you found this to be useful across browsers?  Would love to hear your thoughts.  Thanks!</description>
		<content:encoded><![CDATA[<p>Hello, I was just curious&#8230; I was looking at your source code, and seeing what technique you were using for your layout, specifically in regards to clearing floats.  I saw that you use in some of your containers width:100% and also clear:left.  Have you found this to be useful across browsers?  Would love to hear your thoughts.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: XGhozt</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4352</link>
		<dc:creator>XGhozt</dc:creator>
		<pubDate>Tue, 18 Mar 2008 18:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4352</guid>
		<description>All mine got 100%. :)</description>
		<content:encoded><![CDATA[<p>All mine got 100%. <img src='http://www.webappers.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4315</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Mon, 17 Mar 2008 18:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4315</guid>
		<description>Pretty good. I would suggest a "bad words" array of passwords that can't be used. For example, "password", "123456", etc. will automatically fail.</description>
		<content:encoded><![CDATA[<p>Pretty good. I would suggest a &#8220;bad words&#8221; array of passwords that can&#8217;t be used. For example, &#8220;password&#8221;, &#8220;123456&#8243;, etc. will automatically fail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Williams</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4312</link>
		<dc:creator>Ryan Williams</dc:creator>
		<pubDate>Mon, 17 Mar 2008 13:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4312</guid>
		<description>These things are OK, but I don't think they should ever force you to adhere to its guidelines.

I always use a password comprised of 11 seemingly random characters (I have a clever little formula), which realistically is never going to be cracked. The beauty of my formula is it's unique for each site but always memorable, meaning even if it's compromised it's no good for any other domain.

These tools prevent me from using that formula, which causes me some minor headaches when logging into those sites. Often I just don't bother.</description>
		<content:encoded><![CDATA[<p>These things are OK, but I don&#8217;t think they should ever force you to adhere to its guidelines.</p>
<p>I always use a password comprised of 11 seemingly random characters (I have a clever little formula), which realistically is never going to be cracked. The beauty of my formula is it&#8217;s unique for each site but always memorable, meaning even if it&#8217;s compromised it&#8217;s no good for any other domain.</p>
<p>These tools prevent me from using that formula, which causes me some minor headaches when logging into those sites. Often I just don&#8217;t bother.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: asterisk</title>
		<link>http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4310</link>
		<dc:creator>asterisk</dc:creator>
		<pubDate>Mon, 17 Mar 2008 08:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.webappers.com/2008/03/17/integrate-password-strength-checker-into-registration-forms/#comment-4310</guid>
		<description>Buggy. m3sS3ng gets 40%, and m3sS3ng3R gets 20%</description>
		<content:encoded><![CDATA[<p>Buggy. m3sS3ng gets 40%, and m3sS3ng3R gets 20%</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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