<?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: Form Security with Autocomplete</title>
	<atom:link href="http://www.csskarma.com/blog/autocomplete-off/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.csskarma.com/blog/autocomplete-off/</link>
	<description>display your &#60;style&#62;</description>
	<lastBuildDate>Mon, 12 Jul 2010 04:09:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Joe Devon</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-60455</link>
		<dc:creator>Joe Devon</dc:creator>
		<pubDate>Tue, 12 May 2009 01:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-60455</guid>
		<description>Sweet!</description>
		<content:encoded><![CDATA[<p>Sweet!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mauro Accornero</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-56868</link>
		<dc:creator>Mauro Accornero</dc:creator>
		<pubDate>Tue, 21 Apr 2009 09:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-56868</guid>
		<description>Nice trick, I like the solution with noscript.</description>
		<content:encoded><![CDATA[<p>Nice trick, I like the solution with noscript.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-54549</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 10 Apr 2009 21:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-54549</guid>
		<description>Nice. Thanks for the code.</description>
		<content:encoded><![CDATA[<p>Nice. Thanks for the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-54507</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 10 Apr 2009 18:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-54507</guid>
		<description>yea, that&#039;s true that &lt;em&gt;you&lt;/em&gt; might do it that way, but most people aren&#039;t aware of that and let this data get saved and easily accessed. Most people aren&#039;t even aware they have options in the browser.

Being responsible developers, we should look out for our users and take the extra 10 seconds to add something like this in.</description>
		<content:encoded><![CDATA[<p>yea, that&#8217;s true that <em>you</em> might do it that way, but most people aren&#8217;t aware of that and let this data get saved and easily accessed. Most people aren&#8217;t even aware they have options in the browser.</p>
<p>Being responsible developers, we should look out for our users and take the extra 10 seconds to add something like this in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-54505</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Fri, 10 Apr 2009 17:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-54505</guid>
		<description>I don&#039;t understand the point of this. Autocomplete is handled by the browser. The data is kept client-side. The user agent is able to do 2 things that make this technique moot. 1) You could omit @autocomplete=off and the browser (or extensions) could ignore that command and not remember the data. 2) You could utilize @autocomplete=off and the user agent agent could ignore that command and remember the data anyway.  No matter whether you use @autocomplete or not the user agent (or extensions thereof) can ignore your request and do its own thing. Further the user agent behavior is configurable by the end user with their browser/extension settings. As an end user, if I&#039;m worried about my browser remembering my data, then I won&#039;t leave it up to the site owner and hope they use @autocomplete=off. I&#039;ll configure my browser to not remember the data!</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand the point of this. Autocomplete is handled by the browser. The data is kept client-side. The user agent is able to do 2 things that make this technique moot. 1) You could omit @autocomplete=off and the browser (or extensions) could ignore that command and not remember the data. 2) You could utilize @autocomplete=off and the user agent agent could ignore that command and remember the data anyway.  No matter whether you use @autocomplete or not the user agent (or extensions thereof) can ignore your request and do its own thing. Further the user agent behavior is configurable by the end user with their browser/extension settings. As an end user, if I&#8217;m worried about my browser remembering my data, then I won&#8217;t leave it up to the site owner and hope they use @autocomplete=off. I&#8217;ll configure my browser to not remember the data!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-54504</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 10 Apr 2009 17:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-54504</guid>
		<description>Some folks are required to have valid code, for whatever reason. For those people I&#039;d recommend the JS solution, for everyone else, just code it right in the field. I agree, it&#039;s not worth using JS in this situation but it&#039;s nice to be aware of the option.

A similar technique is used for adding in ARIA code for accessibility (using JS to keep the xhtml valid).</description>
		<content:encoded><![CDATA[<p>Some folks are required to have valid code, for whatever reason. For those people I&#8217;d recommend the JS solution, for everyone else, just code it right in the field. I agree, it&#8217;s not worth using JS in this situation but it&#8217;s nice to be aware of the option.</p>
<p>A similar technique is used for adding in ARIA code for accessibility (using JS to keep the xhtml valid).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Sigurdhsson</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-54503</link>
		<dc:creator>Simon Sigurdhsson</dc:creator>
		<pubDate>Fri, 10 Apr 2009 17:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-54503</guid>
		<description>Innovative solution. I still feel that adding security features using JS is dumb. You still have to use the noscript tag and in that you still have invalid XHTML, so why bother in the first place?</description>
		<content:encoded><![CDATA[<p>Innovative solution. I still feel that adding security features using JS is dumb. You still have to use the noscript tag and in that you still have invalid XHTML, so why bother in the first place?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://www.csskarma.com/blog/autocomplete-off/comment-page-1/#comment-54489</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Fri, 10 Apr 2009 16:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.csskarma.com/blog/?p=480#comment-54489</guid>
		<description>php can&#039;t check for javascript as it&#039;s server not clientside. Noscript is the way to do this.</description>
		<content:encoded><![CDATA[<p>php can&#8217;t check for javascript as it&#8217;s server not clientside. Noscript is the way to do this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
