<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>DOM Scripting comments: Easier CSS rules through DOM Scripting</title>
        <link>http://domscripting.com/blog/display/38</link>
        <description>Dustin Diaz has written a nice little script for adding classes to form fields.</description>
        <language>en</language>
        <item>
            <title>Dan Dean</title>
            <link>http://domscripting.com/blog/display.php/38#comment229</link>
            <content:encoded><![CDATA[<p>Wow Brett, you&#8217;re an angry guy.</p>

<p>Anyhoo, does anyone know if it&#8217;s possible to detect support for particular selectors, like &quot;first-child&quot;?</p>

<p>Hmmmm.
Ok, Bye.</p>
]]></content:encoded>
            <pubDate>Sat, 21 Jan 2006 00:37:21 GMT</pubDate>
        </item>
        <item>
            <title>Brett Merkey</title>
            <link>http://domscripting.com/blog/display.php/38#comment200</link>
            <content:encoded><![CDATA[<p>Be aware that the example, as given by Dustin, does not work in IE6 &#8212; the intended target of the script.</p>

<p>The script is fine. The style rules fail. Reasonably, he combines modern and legacy selectors in one ruleset. IE, however, throws out the entire ruleset when it encounters the unfamiliar attribute selector. They have to be separated as in the example below:</p>

<p>input.checkbox {border:1px dotted red;}
input[type=&#8217;checkbox&#8217;] {outline:1px solid red;}</p>

<p>Note also the IE does not recognize many style properties for input tags anyway &#8212; and when it does, it may be the wrong property.</p>

<p>This comment form sucks. Why do I have to type in microscopic font in a microscopic form element? Gawd I hate cramped forms&#8230;</p>
]]></content:encoded>
            <pubDate>Sun, 25 Dec 2005 23:10:36 GMT</pubDate>
        </item>
   </channel>
</rss>