<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

<channel>
    

    <title>The nGen Works Blog: IE, z&#45;index, and making a DIV a link</title>
    <link>http://www.ngenworks.com/blog/detail/ie_z_index_and_making_a_div_a_link/</link>
    <description>How to make a DIV a link and resolve some z&#45;index issues in IE.</description>
    <dc:language>en-us</dc:language>
    <dc:creator>fred@ngenworks.com</dc:creator>
    <dc:rights>Copyright 2009</dc:rights>
    <dc:date>2009-11-17T14:00:00-05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.pmachine.com/" />



    <item>
      <title>Comment by Michela</title>
      <link>http://www.mikidesign.eu</link>
      <description><![CDATA[	<p>{body}</p>]]></description>
      <content:encoded><![CDATA[Nice info thanks]]></content:encoded>
     <dc:date>2009-12-24T13:13:37-05:00</dc:date>
    </item>

    <item>
      <title>Comment by Jeremy Bechtold</title>
      <link>news@obdcreative.com</link>
      <description><![CDATA[	<p>{body}</p>]]></description>
      <content:encoded><![CDATA[and there again lies the beauty of the web. so many ways to accomplish the same task, and legit reasons for passionate arguments for all of them. I love when designers offer real-world implementations as the basis for a blog post and the community responds with insight and alternatives. you got yourselves another feed subscriber. keep it up!]]></content:encoded>
     <dc:date>2009-11-25T12:46:37-05:00</dc:date>
    </item>

    <item>
      <title>Comment by Fred Boyle</title>
      <link>http://www.ngenworks.com</link>
      <description><![CDATA[	<p>{body}</p>]]></description>
      <content:encoded><![CDATA[Jeremy, 

Part of the reason I chose to stick with the DIV as opposed to an A tag was the structure of the information. The situation made sense to have a DIV. I wanted a DIV to be a link and not a link to be a DIV. 

So that's partly why I went the route I did. Your suggestion would also be fine, however in this case the DIV made more sense to me.

Thanks for the feedback!]]></content:encoded>
     <dc:date>2009-11-25T11:57:00-05:00</dc:date>
    </item>

    <item>
      <title>Comment by Jeremy Bechtold</title>
      <link>news@obdcreative.com</link>
      <description><![CDATA[	<p>{body}</p>]]></description>
      <content:encoded><![CDATA[I know I have to assume that you want all markup to validate, but by way of having all the extra markup you defeat the purpose of forcing yourself to write valid code over making things easier on yourself and writing more simple code...

why not display: block; the a element with the same structure that you use for the containing div.project? use the a as the container itself. so you'll throw a couple block-level elements inside it—big deal, you're promoting it to block-level via css, so it'll still work. you're cutting down on extra divs, extra css, and not having a big workaround just to validate. If you comment your markup for the validation snobs out there (and I can be one of them at times) so that they're aware that you're trading invalid code for less unnecessary markup, then you'll likely earn praise rather than flames. and if not, screw 'em. too many people make things too difficult (again, myself included at times) in order to validate. be happy that you found a better solution instead and go with it. it's not the only option, but it is an option.]]></content:encoded>
     <dc:date>2009-11-19T23:37:07-05:00</dc:date>
    </item>

    <item>
      <title>Comment by Jason</title>
      <link>jasonlee@gmail.com</link>
      <description><![CDATA[	<p>{body}</p>]]></description>
      <content:encoded><![CDATA[<a href="http://stackoverflow.com/questions/180211/jquery-div-click-with-anchors">http://stackoverflow.com/questions/180211/jquery-div-click-with-anchors</a>]]></content:encoded>
     <dc:date>2009-11-17T11:22:16-05:00</dc:date>
    </item>


</channel>
</rss>