<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[Content with Style - Comments on DOM scripting or how to keep the code clean]]></title>
    <link>http://www.contentwithstyle.co.uk/feeds/rss/comments/6</link>
    <description><![CDATA[]]></description>
    <pubDate>Fri, 12 Mar 2010 21:13:27 +0000</pubDate>
    <generator>Zend_Feed</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Content with Style - Comment #1 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-27</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-27</guid>
      <description><![CDATA[Nice article, Pascal!<br />
<br />
Here&#8217;s another application to the technique you describe. You can create nice menus automatically from the following code:<br />
<br />
<pre><br />
&lt;ul id="menu"&gt;<br />
  &lt;li&gt;&lt;a href="home.html"&gt;Home&lt;/a&gt;<br />
  &lt;li&gt;&lt;a href="products.html"&gt;Products&lt;/a&gt;<br />
&lt;/ul&gt;<br />
</pre><br />
<br />
What is necessary is to take the URL from the HREF of A tag wrapped with LI and create onClick function on that LI with appropriate HREF. The ID of UL element will allow to find only necessary LI&#8217;s and A&#8217;s. Doing so will guaranty that if user clicks anywhere on the cell (not only on the A tag text) he will be forwarded to a new page. And the processing can be automated down to onLoad=&#8221;processMenu(&#8216;menu&#8217;)&#8221; in BODY tag. In conjuntion with correct cursor shape set for LI in CSS (to mimic the one when over the link) the overal look and feel will be excellent.<br />
<br />
We use this technique for several years already and it&#8217;s proved to work wonderfully.]]></description>
      <content:encoded><![CDATA[Nice article, Pascal!<br />
<br />
Here&#8217;s another application to the technique you describe. You can create nice menus automatically from the following code:<br />
<br />
<pre><br />
&lt;ul id="menu"&gt;<br />
  &lt;li&gt;&lt;a href="home.html"&gt;Home&lt;/a&gt;<br />
  &lt;li&gt;&lt;a href="products.html"&gt;Products&lt;/a&gt;<br />
&lt;/ul&gt;<br />
</pre><br />
<br />
What is necessary is to take the URL from the HREF of A tag wrapped with LI and create onClick function on that LI with appropriate HREF. The ID of UL element will allow to find only necessary LI&#8217;s and A&#8217;s. Doing so will guaranty that if user clicks anywhere on the cell (not only on the A tag text) he will be forwarded to a new page. And the processing can be automated down to onLoad=&#8221;processMenu(&#8216;menu&#8217;)&#8221; in BODY tag. In conjuntion with correct cursor shape set for LI in CSS (to mimic the one when over the link) the overal look and feel will be excellent.<br />
<br />
We use this technique for several years already and it&#8217;s proved to work wonderfully.]]></content:encoded>
      <pubDate>Sun, 22 May 2005 06:30:54 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #2 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-29</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-29</guid>
      <description><![CDATA[hmm, why the hassle?<br />
Using css and switching the &#8220;li&#8221; to inline, the &#8220;a&#8221; within the &#8220;li&#8221; to block should do the same, right? And you don&#8217;t &#8220;pollute&#8221; the body tag. And would ensure that, if JS is off, it still works on new generation browsers. Does that make sense?]]></description>
      <content:encoded><![CDATA[hmm, why the hassle?<br />
Using css and switching the &#8220;li&#8221; to inline, the &#8220;a&#8221; within the &#8220;li&#8221; to block should do the same, right? And you don&#8217;t &#8220;pollute&#8221; the body tag. And would ensure that, if JS is off, it still works on new generation browsers. Does that make sense?]]></content:encoded>
      <pubDate>Sun, 22 May 2005 09:24:31 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #3 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-34</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-34</guid>
      <description><![CDATA[Since the target attribute is not allowed in XHTML 1.0 Strict, would it be better to apply something like <code>class="popupLink"</code> instead?]]></description>
      <content:encoded><![CDATA[Since the target attribute is not allowed in XHTML 1.0 Strict, would it be better to apply something like <code>class="popupLink"</code> instead?]]></content:encoded>
      <pubDate>Mon, 23 May 2005 08:48:07 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #4 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-38</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-38</guid>
      <description><![CDATA[I use the <a href="http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel">rel attribute</a> instead.  Rel=&#8221;external&#8221; for popups is both semantic and human readable&#8230; I&#8217;ve also got a rel=&#8221;choice&#8221; which, at runtime, triggers a script to run through and add a little popup icon after the link to open in a new window, allowing people to choose between same and new windows.]]></description>
      <content:encoded><![CDATA[I use the <a href="http://www.w3.org/TR/REC-html40/struct/links.html#adef-rel">rel attribute</a> instead.  Rel=&#8221;external&#8221; for popups is both semantic and human readable&#8230; I&#8217;ve also got a rel=&#8221;choice&#8221; which, at runtime, triggers a script to run through and add a little popup icon after the link to open in a new window, allowing people to choose between same and new windows.]]></content:encoded>
      <pubDate>Mon, 23 May 2005 11:10:37 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #5 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-39</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-39</guid>
      <description><![CDATA[Haahahahaa. Hey, Mike, you seem like a smart guy, can I meet you for a pint? Let&#8217;s set up a website!<br />
<br />
I have been using the rel attribute for a couple of things in the past, including image rollovers and other things where I wanted to trick the validator; until I got worried that I don&#8217;t follow the idea of the attribute. But your way of using it seems actually close enough to what it&#8217;s supposed to be.]]></description>
      <content:encoded><![CDATA[Haahahahaa. Hey, Mike, you seem like a smart guy, can I meet you for a pint? Let&#8217;s set up a website!<br />
<br />
I have been using the rel attribute for a couple of things in the past, including image rollovers and other things where I wanted to trick the validator; until I got worried that I don&#8217;t follow the idea of the attribute. But your way of using it seems actually close enough to what it&#8217;s supposed to be.]]></content:encoded>
      <pubDate>Mon, 23 May 2005 16:17:43 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #6 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-66</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-66</guid>
      <description><![CDATA[Er, now anyone who&#8217;s not read the <a href="/About">about</a> page will be thinking you&#8217;re my stalker!]]></description>
      <content:encoded><![CDATA[Er, now anyone who&#8217;s not read the <a href="/About">about</a> page will be thinking you&#8217;re my stalker!]]></content:encoded>
      <pubDate>Tue, 24 May 2005 22:19:40 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #7 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-84</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-84</guid>
      <description><![CDATA[Pascal, you are right. The same could be established by pure CSS also. You points make sense.]]></description>
      <content:encoded><![CDATA[Pascal, you are right. The same could be established by pure CSS also. You points make sense.]]></content:encoded>
      <pubDate>Thu, 26 May 2005 09:59:55 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #8 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-86</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-86</guid>
      <description><![CDATA[In fact i always suggest <a href="http://www.deelan.com/docs/html/best/en/#url">this way</a> to insert pop-ups in a web page.<br />
<br />
Throw into the popup variant and you are done, accessible popup windows for the masses!<br />
<br />
cheers,<br />
deelan.]]></description>
      <content:encoded><![CDATA[In fact i always suggest <a href="http://www.deelan.com/docs/html/best/en/#url">this way</a> to insert pop-ups in a web page.<br />
<br />
Throw into the popup variant and you are done, accessible popup windows for the masses!<br />
<br />
cheers,<br />
deelan.]]></content:encoded>
      <pubDate>Thu, 26 May 2005 11:07:27 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #9 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-88</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-88</guid>
      <description><![CDATA[Deelan,<br />
Your suggested solution is getting used more and more, which is good, and Pascal had mentioned it in his article as well (ok, minus the target=&#8221;_blank&#8221;, but that&#8217;s really a question of strict or transitional xhtml).<br />
<br />
What I like about Pascals approach is, that you can separate content from functionality. The html stays the same, clean and lean. I&#8217;m sure instead of the target you could use other ways of determining which links are popups and which stay in the same window, such as an id (don&#8217;t forget to keep it unique) or the surrounding html structure.<br />
<br />
Cheers,<br />
Matthias]]></description>
      <content:encoded><![CDATA[Deelan,<br />
Your suggested solution is getting used more and more, which is good, and Pascal had mentioned it in his article as well (ok, minus the target=&#8221;_blank&#8221;, but that&#8217;s really a question of strict or transitional xhtml).<br />
<br />
What I like about Pascals approach is, that you can separate content from functionality. The html stays the same, clean and lean. I&#8217;m sure instead of the target you could use other ways of determining which links are popups and which stay in the same window, such as an id (don&#8217;t forget to keep it unique) or the surrounding html structure.<br />
<br />
Cheers,<br />
Matthias]]></content:encoded>
      <pubDate>Thu, 26 May 2005 13:56:21 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #10 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-89</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-89</guid>
      <description><![CDATA[Deelan:<br />
Matthias is right about that. you could trigger the same by using any attribute, a surrounding or a childnode element &#8230; target _blank is just an example and for sure not best practice for accessible HTML.<br />
<br />
The weak point of way you suggest is the &#8220;pollution&#8221; with the onclick handler within the markup, and the redundant string for the href, which is exactly what you can get rid of...]]></description>
      <content:encoded><![CDATA[Deelan:<br />
Matthias is right about that. you could trigger the same by using any attribute, a surrounding or a childnode element &#8230; target _blank is just an example and for sure not best practice for accessible HTML.<br />
<br />
The weak point of way you suggest is the &#8220;pollution&#8221; with the onclick handler within the markup, and the redundant string for the href, which is exactly what you can get rid of...]]></content:encoded>
      <pubDate>Thu, 26 May 2005 16:02:21 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #11 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-130</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-130</guid>
      <description><![CDATA[great site! I mentioned this on my site today and thought you would enjoy my take on this subject. I wrote a javascript function that makes adding XHTML tags easier. I would like to expand on it. Please let me know what you think. It&#8217;s at http://www.heywink.com/files/DOModder.zip you can read about it at http://www.heywink.com/files/DOModder.pdf]]></description>
      <content:encoded><![CDATA[great site! I mentioned this on my site today and thought you would enjoy my take on this subject. I wrote a javascript function that makes adding XHTML tags easier. I would like to expand on it. Please let me know what you think. It&#8217;s at http://www.heywink.com/files/DOModder.zip you can read about it at http://www.heywink.com/files/DOModder.pdf]]></content:encoded>
      <pubDate>Mon, 06 Jun 2005 21:20:12 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #12 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-246</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-246</guid>
      <description><![CDATA[Great article, althought I won&#8217;t use it, because I don&#8217;t like to pop out windows. As a user, I know how to open a new window when clicking on a link, when I want to&#8230;<br />
<br />
Note that the first two old ways are really annoying, because it prevents to allow to drag the link to a tab (in Mozilla or Firefox or custom IE base browser), which is the usual way I use to open a link in another window (that and Ctrl+Click, of course);.<br />
<br />
I also just want to point out two typos:<br />
propper and getElemet (3 times&#8230;)<br />
HTH.]]></description>
      <content:encoded><![CDATA[Great article, althought I won&#8217;t use it, because I don&#8217;t like to pop out windows. As a user, I know how to open a new window when clicking on a link, when I want to&#8230;<br />
<br />
Note that the first two old ways are really annoying, because it prevents to allow to drag the link to a tab (in Mozilla or Firefox or custom IE base browser), which is the usual way I use to open a link in another window (that and Ctrl+Click, of course);.<br />
<br />
I also just want to point out two typos:<br />
propper and getElemet (3 times&#8230;)<br />
HTH.]]></content:encoded>
      <pubDate>Mon, 26 Sep 2005 04:52:10 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #13 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-280</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-280</guid>
      <description><![CDATA[Phillipe: <br />
Thanks for pointing out the possibility with dragging links to a tab (I never thought of that actually).<br />
<br />
Fair enough that you don&#8217;t do popups, but in fact the article was more about showing non-intrusive javascript and the popups were just an example. So if you didn&#8217;t know about this before I hope you could use bits and bobs.<br />
<br />
For the typos: Shame on me! Removed them.]]></description>
      <content:encoded><![CDATA[Phillipe: <br />
Thanks for pointing out the possibility with dragging links to a tab (I never thought of that actually).<br />
<br />
Fair enough that you don&#8217;t do popups, but in fact the article was more about showing non-intrusive javascript and the popups were just an example. So if you didn&#8217;t know about this before I hope you could use bits and bobs.<br />
<br />
For the typos: Shame on me! Removed them.]]></content:encoded>
      <pubDate>Thu, 27 Oct 2005 03:29:11 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #14 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-323</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-323</guid>
      <description><![CDATA[Keeping the markup hook free:<br />
<a href="http://www.tjkdesign.com/articles/popups.asp">Opening pop up windows with no extra markup</a>]]></description>
      <content:encoded><![CDATA[Keeping the markup hook free:<br />
<a href="http://www.tjkdesign.com/articles/popups.asp">Opening pop up windows with no extra markup</a>]]></content:encoded>
      <pubDate>Tue, 08 Nov 2005 09:57:28 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #15 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-326</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-326</guid>
      <description><![CDATA[Thierry &#8230; nice one. <br />
Picking up the discussion above: Is there any reason for using &#8220;class&#8221; instead of &#8220;rel&#8221; to trigger what&#8217;s popup and what&#8217;s not?]]></description>
      <content:encoded><![CDATA[Thierry &#8230; nice one. <br />
Picking up the discussion above: Is there any reason for using &#8220;class&#8221; instead of &#8220;rel&#8221; to trigger what&#8217;s popup and what&#8217;s not?]]></content:encoded>
      <pubDate>Thu, 10 Nov 2005 07:11:09 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #16 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-333</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-333</guid>
      <description><![CDATA[Pascal,<br />
The specs say (about &#8220;rel&#8221;):<br />
<cite>This attribute describes the relationship from the current document to the anchor specified by the href attribute. The value of this attribute is a space-separated list of link types.</cite><br />
This <a href="http://www.w3.org/TR/REC-html40/types.html#type-links">section</a> is about link types, it lists their conventional interpretations<br />
The way I read this, I&#8217;d say using  &#8220;class&#8221; would be more appropriate.<br />
<br />
BTW, thanks for the compliment about my article.]]></description>
      <content:encoded><![CDATA[Pascal,<br />
The specs say (about &#8220;rel&#8221;):<br />
<cite>This attribute describes the relationship from the current document to the anchor specified by the href attribute. The value of this attribute is a space-separated list of link types.</cite><br />
This <a href="http://www.w3.org/TR/REC-html40/types.html#type-links">section</a> is about link types, it lists their conventional interpretations<br />
The way I read this, I&#8217;d say using  &#8220;class&#8221; would be more appropriate.<br />
<br />
BTW, thanks for the compliment about my article.]]></content:encoded>
      <pubDate>Wed, 16 Nov 2005 23:43:17 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #17 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-534</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-534</guid>
      <description><![CDATA[Hi there, great article!<br />
I have a question, I&#8217;ve always used class as a &#8220;second&#8221; identifier, id for unique and class for group of items, am I wrong?<br />
<br />
I really enjoy the possibility to describe an object with non-intrusive Js (I dont really knew how to name this) using many class identifiers heh.<br />
<br />
Thanks!]]></description>
      <content:encoded><![CDATA[Hi there, great article!<br />
I have a question, I&#8217;ve always used class as a &#8220;second&#8221; identifier, id for unique and class for group of items, am I wrong?<br />
<br />
I really enjoy the possibility to describe an object with non-intrusive Js (I dont really knew how to name this) using many class identifiers heh.<br />
<br />
Thanks!]]></content:encoded>
      <pubDate>Sat, 15 Apr 2006 11:30:14 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #18 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-536</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-536</guid>
      <description><![CDATA[Lucas: According to <a href="http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2">the w3c definition for id and class</a> both elements can be used &#8220;For general purpose processing by user agents (e.g. for identifying fields when extracting data from HTML pages into a database, translating HTML documents into other formats, etc.)&#8221;.<br />
<br />
So scripting wise you have the choice what to do with them. CSS wise there is always the <a href="http://www.stuffandnonsense.co.uk/archives/css_specificity_wars.html">specifity</a> that has to be taken into account. And yes, id has to be unique within the document.]]></description>
      <content:encoded><![CDATA[Lucas: According to <a href="http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2">the w3c definition for id and class</a> both elements can be used &#8220;For general purpose processing by user agents (e.g. for identifying fields when extracting data from HTML pages into a database, translating HTML documents into other formats, etc.)&#8221;.<br />
<br />
So scripting wise you have the choice what to do with them. CSS wise there is always the <a href="http://www.stuffandnonsense.co.uk/archives/css_specificity_wars.html">specifity</a> that has to be taken into account. And yes, id has to be unique within the document.]]></content:encoded>
      <pubDate>Sat, 15 Apr 2006 14:58:40 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #19 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-2318</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-2318</guid>
      <description><![CDATA[I guess then it must be possible as well to combine the lightbox &#8220;popup&#8221; and the DOM popup to achieve a javascriptless popup with background?]]></description>
      <content:encoded><![CDATA[I guess then it must be possible as well to combine the lightbox &#8220;popup&#8221; and the DOM popup to achieve a javascriptless popup with background?]]></content:encoded>
      <pubDate>Tue, 18 Sep 2007 09:18:09 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #20 on DOM scripting or how to keep the code clean]]></title>
      <link>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-2332</link>
      <guid>http://www.contentwithstyle.co.uk/content/dom-scripting-or-how-to-keep-the-code-clean/#comment-2332</guid>
      <description><![CDATA[Esther: The lightbox popup as well as any DOM scripting is JavaScript. However, if you wonder about the possibility of using lightbox popup together with attaching events to the DOM nodes, all without explicit script tags in the body: Yeah, that&#8217;s possible for sure.]]></description>
      <content:encoded><![CDATA[Esther: The lightbox popup as well as any DOM scripting is JavaScript. However, if you wonder about the possibility of using lightbox popup together with attaching events to the DOM nodes, all without explicit script tags in the body: Yeah, that&#8217;s possible for sure.]]></content:encoded>
      <pubDate>Fri, 21 Sep 2007 02:58:04 +0000</pubDate>
    </item>
  </channel>
</rss>
