<?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: Progressive Enhancement with Prototype and Custom HTML Attributes</title>
	<atom:link href="http://pathfindersoftware.com/2008/07/progressive-enhancement-with-prototype-and-custom-html-attributes/feed/" rel="self" type="application/rss+xml" />
	<link>http://pathfindersoftware.com/2008/07/progressive-enhancement-with-prototype-and-custom-html-attributes/</link>
	<description>The Fastest Way to Launch Successful Software</description>
	<lastBuildDate>Thu, 19 Jan 2012 16:36:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Anthony Caliendo</title>
		<link>http://pathfindersoftware.com/2008/07/progressive-enhancement-with-prototype-and-custom-html-attributes/#comment-8472</link>
		<dc:creator>Anthony Caliendo</dc:creator>
		<pubDate>Tue, 15 Jul 2008 17:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1032#comment-8472</guid>
		<description>I have to agree with your valid HTML argument, and using class names which contain the configuration information (e.g. &#039;class=&quot;default_foo&quot;&#039;) can also be used to do the same thing completely through javascript.

However, I personally feel that specifying unique content information in an attribute of an element is more &quot;natural&quot;.  To me, using the class just feels &quot;wrong&quot; (even though it is definitely more correct from a standards point of view).

class=&quot;default_foo&quot; may make more semantic sense to a computer, but to a developer I think it is more confusing than default=&quot;foo&quot; (especially when taken in the context of a text field).  This most likely is the result of the connotation of &quot;class&quot;, which doesn&#039;t really fit well with providing configuration for this specific example.

This, of course, is just my opinion.  Regardless, you are correct that it is not strictly valid nor standard HTML.</description>
		<content:encoded><![CDATA[<p>I have to agree with your valid HTML argument, and using class names which contain the configuration information (e.g. &#8216;class=&#8221;default_foo&#8221;&#8216;) can also be used to do the same thing completely through javascript.</p>
<p>However, I personally feel that specifying unique content information in an attribute of an element is more &#8220;natural&#8221;.  To me, using the class just feels &#8220;wrong&#8221; (even though it is definitely more correct from a standards point of view).</p>
<p>class=&#8221;default_foo&#8221; may make more semantic sense to a computer, but to a developer I think it is more confusing than default=&#8221;foo&#8221; (especially when taken in the context of a text field).  This most likely is the result of the connotation of &#8220;class&#8221;, which doesn&#8217;t really fit well with providing configuration for this specific example.</p>
<p>This, of course, is just my opinion.  Regardless, you are correct that it is not strictly valid nor standard HTML.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joey</title>
		<link>http://pathfindersoftware.com/2008/07/progressive-enhancement-with-prototype-and-custom-html-attributes/#comment-8471</link>
		<dc:creator>joey</dc:creator>
		<pubDate>Tue, 15 Jul 2008 01:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1032#comment-8471</guid>
		<description>Problem with this is that it is not valid HTML.  You get into creating all these non-semantic attributes as well that can confuse other developers.

This should be separated out into JavaScript completely and add a CSS class as the hook.</description>
		<content:encoded><![CDATA[<p>Problem with this is that it is not valid HTML.  You get into creating all these non-semantic attributes as well that can confuse other developers.</p>
<p>This should be separated out into JavaScript completely and add a CSS class as the hook.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (User agent is rejected)
Page Caching using memcached (User agent is rejected)

Served from: pathfindersoftware.com @ 2012-02-10 03:09:30 -->
