<?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: IE7 Still Has Problems With Option Tag Values</title>
	<atom:link href="http://blog.gordaen.com/2006/10/23/ie7-still-has-problems-with-option-tag-values/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gordaen.com/2006/10/23/ie7-still-has-problems-with-option-tag-values/</link>
	<description>Ramblings about art, education, Linux and a lot more</description>
	<pubDate>Mon, 12 May 2008 12:48:43 +0000</pubDate>
		<item>
		<title>By: Bernie Zimmermann</title>
		<link>http://blog.gordaen.com/2006/10/23/ie7-still-has-problems-with-option-tag-values/#comment-196</link>
		<dc:creator>Bernie Zimmermann</dc:creator>
		<pubDate>Tue, 24 Oct 2006 03:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gordaen.com/2006/10/23/ie7-still-has-problems-with-option-tag-values/#comment-196</guid>
		<description>I find it really hard to believe they made such a glaring omission from their browser.  And no, not even IE7.  I'm surprised this type of bug slipped into IE6.  I've always taken for granted that you could leave the value attribute off if you wanted to, but then again I haven't used that technique in a long time (I think).  That's the only explanation I can think of for why I wouldn't have noticed this, because I use the option tag quite frequently when developing form-based web pages.

I guess the only silver lining is that there is a standards-based workaround to the problem.</description>
		<content:encoded><![CDATA[<p>I find it really hard to believe they made such a glaring omission from their browser.  And no, not even IE7.  I&#8217;m surprised this type of bug slipped into IE6.  I&#8217;ve always taken for granted that you could leave the value attribute off if you wanted to, but then again I haven&#8217;t used that technique in a long time (I think).  That&#8217;s the only explanation I can think of for why I wouldn&#8217;t have noticed this, because I use the option tag quite frequently when developing form-based web pages.</p>
<p>I guess the only silver lining is that there is a standards-based workaround to the problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
