<?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: Semantic Forms</title>
	<atom:link href="http://blog.dynamic50.com/2009/07/23/semantic-forms/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dynamic50.com/2009/07/23/semantic-forms/</link>
	<description>Ruby on Rails, London - The Blog by Dynamic50</description>
	<lastBuildDate>Mon, 21 Jun 2010 10:10:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matthias Willerich</title>
		<link>http://blog.dynamic50.com/2009/07/23/semantic-forms/comment-page-1/#comment-29</link>
		<dc:creator>Matthias Willerich</dc:creator>
		<pubDate>Tue, 04 Aug 2009 19:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynamic50.com/?p=403#comment-29</guid>
		<description>I&#039;ve come across the opinion that checkboxes and radiobuttons should be grouped by a fieldset, as they are, well, a set of fields that belong together.

You can nest fieldsets as much as you like, but as I&#039;m sure you&#039;ve encountered, they&#039;re stroppy when it comes to styling them.

Other than that I always welcome it when somebody can take the time to decide on how to do-something-right. It&#039;s things like this that make your life so much easier in the long run, because instead of pondering which solution you should attempt this time, you&#039;ve got a set up that works for you, that you can run with in 80% of all cases.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve come across the opinion that checkboxes and radiobuttons should be grouped by a fieldset, as they are, well, a set of fields that belong together.</p>
<p>You can nest fieldsets as much as you like, but as I&#8217;m sure you&#8217;ve encountered, they&#8217;re stroppy when it comes to styling them.</p>
<p>Other than that I always welcome it when somebody can take the time to decide on how to do-something-right. It&#8217;s things like this that make your life so much easier in the long run, because instead of pondering which solution you should attempt this time, you&#8217;ve got a set up that works for you, that you can run with in 80% of all cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Pickett</title>
		<link>http://blog.dynamic50.com/2009/07/23/semantic-forms/comment-page-1/#comment-28</link>
		<dc:creator>Dan Pickett</dc:creator>
		<pubDate>Thu, 23 Jul 2009 19:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynamic50.com/?p=403#comment-28</guid>
		<description>I completely agree with this convention. Unfortunately, there isn&#039;t a clean way (without some creative class names) to correlate/bind a dt to its subsequent dd.

I&#039;ve also had issues with this as it relates to checkboxes. Usually I prefer the checkbox to the left of my label, and this generally breaks the css conventions I have set up.

Hopefully as the HTML5 spec continues on, we&#039;ll see something that both works structurally and sementically.

great post.</description>
		<content:encoded><![CDATA[<p>I completely agree with this convention. Unfortunately, there isn&#8217;t a clean way (without some creative class names) to correlate/bind a dt to its subsequent dd.</p>
<p>I&#8217;ve also had issues with this as it relates to checkboxes. Usually I prefer the checkbox to the left of my label, and this generally breaks the css conventions I have set up.</p>
<p>Hopefully as the <span class="caps">HTML5 </span>spec continues on, we&#8217;ll see something that both works structurally and sementically.</p>
<p>great post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
