<?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: ASP.NET Nested TextBox Bug</title>
	<atom:link href="http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/</link>
	<description>ASP.NET, HTML, CSS, Visual Studio, CSharp, VB.NET and other programming items of interest.</description>
	<pubDate>Tue, 06 Jan 2009 13:31:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: ginji</title>
		<link>http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/#comment-4</link>
		<dc:creator>ginji</dc:creator>
		<pubDate>Fri, 02 Nov 2007 03:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/#comment-4</guid>
		<description>Hmm, having re-read it now, I see that you are talking about them separately, but it's not overly clear that you are. I would say most developers would have the labels and elements separate, not nested, and I don't really see any advantage in having them nested. What benefit do you see in having them nested?</description>
		<content:encoded><![CDATA[<p>Hmm, having re-read it now, I see that you are talking about them separately, but it&#8217;s not overly clear that you are. I would say most developers would have the labels and elements separate, not nested, and I don&#8217;t really see any advantage in having them nested. What benefit do you see in having them nested?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/#comment-3</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 01 Nov 2007 23:58:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/#comment-3</guid>
		<description>Regarding the not having to nest:

I said as much.

The problem is that it works one way without internationalization and doesn't work once you add it.  And most of us are going to creat our sites without internationalization turned on first only to find out that we have to rework all of our presentation layer once we decide to add internationalization into the mix.</description>
		<content:encoded><![CDATA[<p>Regarding the not having to nest:</p>
<p>I said as much.</p>
<p>The problem is that it works one way without internationalization and doesn&#8217;t work once you add it.  And most of us are going to creat our sites without internationalization turned on first only to find out that we have to rework all of our presentation layer once we decide to add internationalization into the mix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ginji</title>
		<link>http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/#comment-2</link>
		<dc:creator>ginji</dc:creator>
		<pubDate>Thu, 01 Nov 2007 23:03:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dmbcllc.com/2007/11/01/aspnet-nested-textbox-bug/#comment-2</guid>
		<description>You don't have to nest the controls in order to make the label render as a label, just setting the associatedcontrolid is enough. Nesting the controls does produce valid XHTML though.

If you want to group elements of a form together, you should use the 'fieldset' and 'legend' (X)HTML tags

You should be using all of the above to make your forms accessible to those with visual impairments that use a screen reader.</description>
		<content:encoded><![CDATA[<p>You don&#8217;t have to nest the controls in order to make the label render as a label, just setting the associatedcontrolid is enough. Nesting the controls does produce valid XHTML though.</p>
<p>If you want to group elements of a form together, you should use the &#8216;fieldset&#8217; and &#8216;legend&#8217; (X)HTML tags</p>
<p>You should be using all of the above to make your forms accessible to those with visual impairments that use a screen reader.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
