<?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: Spiffy Markup?</title>
	<atom:link href="http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/</link>
	<description>Working together for standards</description>
	<lastBuildDate>Wed, 27 Mar 2013 12:19: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: stk</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-56891</link>
		<dc:creator>stk</dc:creator>
		<pubDate>Sun, 18 Mar 2007 05:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-56891</guid>
		<description>Nope, the code is not very spiffy, but it does work as advertised and thanks to social bookmarking, has achieved a certain degree of notoriety.

I typically weigh the XHTML/CSS footprint and semantics against the benefit or wow-factor of a spiffy technique.  For me, the footprint is too large, the code isn&#039;t elegant and the semantics are horrid.  For me, the ends do not justify the means.

For others, the ends are all that matter. To each his own, I guess and hats off to the author for &quot;finding a way&quot;.

However, until I can find a nicer way, all my corners will be square (at least, for liquid designs).

I do hope that the W3C utilizes the feedback - an easy, semantically-correct, light-weight method of rounding corners for block-level elements will be well received! :D

(And the funny part?  When I first looked at both Spiffy and Nifty, I was sure they would fail validation.  Color me converted, but I thought the &lt;b&gt; tag was long gone.) :p</description>
		<content:encoded><![CDATA[<p>Nope, the code is not very spiffy, but it does work as advertised and thanks to social bookmarking, has achieved a certain degree of notoriety.</p>
<p>I typically weigh the XHTML/CSS footprint and semantics against the benefit or wow-factor of a spiffy technique.  For me, the footprint is too large, the code isn&#8217;t elegant and the semantics are horrid.  For me, the ends do not justify the means.</p>
<p>For others, the ends are all that matter. To each his own, I guess and hats off to the author for &#8220;finding a way&#8221;.</p>
<p>However, until I can find a nicer way, all my corners will be square (at least, for liquid designs).</p>
<p>I do hope that the W3C utilizes the feedback &#8211; an easy, semantically-correct, light-weight method of rounding corners for block-level elements will be well received! :D</p>
<p>(And the funny part?  When I first looked at both Spiffy and Nifty, I was sure they would fail validation.  Color me converted, but I thought the &lt;b&gt; tag was long gone.) :p</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chip Peterson</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-54528</link>
		<dc:creator>Chip Peterson</dc:creator>
		<pubDate>Fri, 09 Mar 2007 22:17:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-54528</guid>
		<description>So, in the end, what is the best way to create rounded corners without using images and still be W3C compliant? I have friends that know html are are asking me all the time I want rounded corners because they look so nice. They don&#039;t know much about Photoshop and graphics and they want to adjust everything by themself.
This seems so complicated I better create the images for them than try to explain what is in here.</description>
		<content:encoded><![CDATA[<p>So, in the end, what is the best way to create rounded corners without using images and still be W3C compliant? I have friends that know html are are asking me all the time I want rounded corners because they look so nice. They don&#8217;t know much about Photoshop and graphics and they want to adjust everything by themself.<br />
This seems so complicated I better create the images for them than try to explain what is in here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-5276</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Mon, 18 Sep 2006 07:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-5276</guid>
		<description>I&#039;m a little late to the party, but I thought I would chime in:



There is a lot of ignorant nonsense in this thread about how this is a ripoff of Nifty Corners and such, but if you actually read the page at spiffycorners.com you&#039;ll see exactly what and why.

I didn&#039;t create the technique, and I don&#039;t pretend to. As for the donate link, It&#039;s for the extreme amount of bandwidth the site uses - and it was suggested by people visiting the site, not myself.

I think it&#039;s a little silly that it has caused so much controversy though. To say I wish I never created it would only be half truth. I mean, it&#039;s uses on youTube (view the source of any page on youTube and scroll down just a short ways) and that&#039;s kind of cool. But it&#039;s got everyone in such a hissy.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a little late to the party, but I thought I would chime in:</p>
<p>There is a lot of ignorant nonsense in this thread about how this is a ripoff of Nifty Corners and such, but if you actually read the page at spiffycorners.com you&#8217;ll see exactly what and why.</p>
<p>I didn&#8217;t create the technique, and I don&#8217;t pretend to. As for the donate link, It&#8217;s for the extreme amount of bandwidth the site uses &#8211; and it was suggested by people visiting the site, not myself.</p>
<p>I think it&#8217;s a little silly that it has caused so much controversy though. To say I wish I never created it would only be half truth. I mean, it&#8217;s uses on youTube (view the source of any page on youTube and scroll down just a short ways) and that&#8217;s kind of cool. But it&#8217;s got everyone in such a hissy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Tankard</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-3004</link>
		<dc:creator>Scott Tankard</dc:creator>
		<pubDate>Sat, 05 Aug 2006 20:53:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-3004</guid>
		<description>I agree the markup is nasty, however I feel it&#039;s still a step up from tables (I mean... at least it fits in thirty lines).

I hope the border-radius and gradient &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt; stuff Mozilla has prototyped is accepted into the &lt;acronym title=&quot;World Wide Web Consortium&quot;&gt;W3C&lt;/acronym&gt; specs -- soon!</description>
		<content:encoded><![CDATA[<p>I agree the markup is nasty, however I feel it&#8217;s still a step up from tables (I mean&#8230; at least it fits in thirty lines).</p>
<p>I hope the border-radius and gradient <acronym title="Cascading Style Sheets">CSS</acronym> stuff Mozilla has prototyped is accepted into the <acronym title="World Wide Web Consortium">W3C</acronym> specs &#8212; soon!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-1876</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Tue, 27 Jun 2006 23:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-1876</guid>
		<description>I don&#039;t give a shit about semantics or what have you. what it does is create a simple way to put content inside of a rounded box on a page...cool, thats just what i want. visitors to my website are not going to care how.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t give a shit about semantics or what have you. what it does is create a simple way to put content inside of a rounded box on a page&#8230;cool, thats just what i want. visitors to my website are not going to care how.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Helen, design manager</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-987</link>
		<dc:creator>Helen, design manager</dc:creator>
		<pubDate>Thu, 18 May 2006 11:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-987</guid>
		<description>I think that amount of html codes will make the maintenance a nightmare! Better use some images.</description>
		<content:encoded><![CDATA[<p>I think that amount of html codes will make the maintenance a nightmare! Better use some images.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Design and Development &#187; Blog Archive &#187; Spiffy Corners</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-775</link>
		<dc:creator>Web Design and Development &#187; Blog Archive &#187; Spiffy Corners</dc:creator>
		<pubDate>Wed, 10 May 2006 19:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-775</guid>
		<description>[...] I found it on WaSP, as Ian Lloyd was lamenting its redundancy and non-standards markup. [...]</description>
		<content:encoded><![CDATA[<p>[...] I found it on WaSP, as Ian Lloyd was lamenting its redundancy and non-standards markup. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Design - standards based web design, development and training &#187; Blog Archive &#187; Some links for light reading (5/4/06)</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-479</link>
		<dc:creator>Max Design - standards based web design, development and training &#187; Blog Archive &#187; Some links for light reading (5/4/06)</dc:creator>
		<pubDate>Sat, 29 Apr 2006 05:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-479</guid>
		<description>[...] Spiffy markup? [...]</description>
		<content:encoded><![CDATA[<p>[...] Spiffy markup? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hwright.net &#187; Standards&#8230; are we getting off-topic?</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-464</link>
		<dc:creator>hwright.net &#187; Standards&#8230; are we getting off-topic?</dc:creator>
		<pubDate>Wed, 26 Apr 2006 23:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-464</guid>
		<description>[...] Everyone says &#8220;the site needs to be developed using standards&#8221; but are some people forgetting what the point was? Separation of content and presentation. HTML - produce content. CSS - layout the content. So, in all the fuss over content and presentation, I guess some forgot about the other part of websites &#8212; Functionality. There is a reason there is a difference between a web designer and a web developer. The web developer adds functionality through any number of technologies available to them. So why is Javascript being lumped into the the design side? Just because it can access the DOM model and modify presentation doesn&#8217;t mean it&#8217;s a good idea. Webstandards.org had a post on Spiffy Corners a little while ago. The comments from that post discussed other hacks like Nifty Corners and semantics. I won&#8217;t rehash it all, but it&#8217;s worth a read if you are hazy on the topic. [...]</description>
		<content:encoded><![CDATA[<p>[...] Everyone says &#8220;the site needs to be developed using standards&#8221; but are some people forgetting what the point was? Separation of content and presentation. HTML &#8211; produce content. CSS &#8211; layout the content. So, in all the fuss over content and presentation, I guess some forgot about the other part of websites &#8212; Functionality. There is a reason there is a difference between a web designer and a web developer. The web developer adds functionality through any number of technologies available to them. So why is Javascript being lumped into the the design side? Just because it can access the DOM model and modify presentation doesn&#8217;t mean it&#8217;s a good idea. Webstandards.org had a post on Spiffy Corners a little while ago. The comments from that post discussed other hacks like Nifty Corners and semantics. I won&#8217;t rehash it all, but it&#8217;s worth a read if you are hazy on the topic. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler</title>
		<link>http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/comment-page-1/#comment-328</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Wed, 12 Apr 2006 22:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/04/05/am-i-spiffy-or-not/#comment-328</guid>
		<description>I dont see a problem with inserting presentational elements via DOM. the only people who will recive the extra code are modern desktop browsers.</description>
		<content:encoded><![CDATA[<p>I dont see a problem with inserting presentational elements via DOM. the only people who will recive the extra code are modern desktop browsers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.345 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-02 13:17:34 -->