<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Do NOT attach &#8220;target&#8221; through script!</title>
	<atom:link href="http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/</link>
	<description>...whatever goes through my head...</description>
	<lastBuildDate>Fri, 22 Jan 2010 11:50:20 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dolphinling</title>
		<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/comment-page-1/#comment-2493</link>
		<dc:creator>dolphinling</dc:creator>
		<pubDate>Tue, 17 Oct 2006 06:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/#comment-2493</guid>
		<description>&lt;p&gt;The &quot;in memory&quot; document is the one that the user actually sees and interacts with; it&#039;s the &lt;em&gt;most&lt;/em&gt; important to keep valid. Especially note, for example, assistive software. It&#039;s not so much an obvious problem with &lt;code&gt;target&lt;/code&gt;, but it&#039;s equivalent to, for example, adding a &lt;code&gt;font&lt;/code&gt; element inside a paragraph through script. The original markup will be valid, but the resulting DOM will be invalid, and it&#039;s the resulting DOM that the assistive software looks at. It&#039;ll see the invalid, non-semantic &lt;code&gt;font&lt;/code&gt;, and not know what to do with it.&lt;/p&gt;
&lt;p&gt;PJ, yes, I&#039;m entirely aware of the irony of writing this from wordpress. :-\&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>The &#8220;in memory&#8221; document is the one that the user actually sees and interacts with; it&#8217;s the <em>most</em> important to keep valid. Especially note, for example, assistive software. It&#8217;s not so much an obvious problem with <code>target</code>, but it&#8217;s equivalent to, for example, adding a <code>font</code> element inside a paragraph through script. The original markup will be valid, but the resulting DOM will be invalid, and it&#8217;s the resulting DOM that the assistive software looks at. It&#8217;ll see the invalid, non-semantic <code>font</code>, and not know what to do with it.</p>
<p>PJ, yes, I&#8217;m entirely aware of the irony of writing this from wordpress. :-\</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Cherny</title>
		<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/comment-page-1/#comment-2490</link>
		<dc:creator>Rob Cherny</dc:creator>
		<pubDate>Mon, 16 Oct 2006 13:07:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/#comment-2490</guid>
		<description>I have to disagree with the content of this post, dolphinling, and agree with Tantek Celik. If you dynamically insert a target attribute your original document is still perfectly valid. The only place the &quot;invalid&quot; document exists is at runtime, in memory, and there&#039;s no reasoning that the dynamic document, which doesn&#039;t even persist, matters in the world of validation. The page still renders (in standards mode no less), will continue to, and the DOM has added the behavior layer which is actually exactly the way it&#039;s supposed to work.</description>
		<content:encoded><![CDATA[<p>I have to disagree with the content of this post, dolphinling, and agree with Tantek Celik. If you dynamically insert a target attribute your original document is still perfectly valid. The only place the &#8220;invalid&#8221; document exists is at runtime, in memory, and there&#8217;s no reasoning that the dynamic document, which doesn&#8217;t even persist, matters in the world of validation. The page still renders (in standards mode no less), will continue to, and the DOM has added the behavior layer which is actually exactly the way it&#8217;s supposed to work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJ</title>
		<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/comment-page-1/#comment-2340</link>
		<dc:creator>PJ</dc:creator>
		<pubDate>Mon, 18 Sep 2006 16:05:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/#comment-2340</guid>
		<description>It&#039;s funny that you&#039;re preaching this from the default WordPress theme.  

It was hard, but I gave up target tags to be &quot;Strict&quot;.</description>
		<content:encoded><![CDATA[<p>It&#8217;s funny that you&#8217;re preaching this from the default WordPress theme.  </p>
<p>It was hard, but I gave up target tags to be &#8220;Strict&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zcorpan</title>
		<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/comment-page-1/#comment-2155</link>
		<dc:creator>zcorpan</dc:creator>
		<pubDate>Tue, 01 Aug 2006 22:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/#comment-2155</guid>
		<description>Sébastien, no, the spec does not require that UAs behave differently depending on the doctype. (Formally, handling of invalid documents is undefined in HTML4.)

Nat, no, the HTML that the XSLT outputs is invalid (or, to put it in another way, the resulting DOM is invalid).</description>
		<content:encoded><![CDATA[<p>Sébastien, no, the spec does not require that UAs behave differently depending on the doctype. (Formally, handling of invalid documents is undefined in HTML4.)</p>
<p>Nat, no, the HTML that the XSLT outputs is invalid (or, to put it in another way, the resulting DOM is invalid).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abba bryant</title>
		<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/comment-page-1/#comment-2154</link>
		<dc:creator>abba bryant</dc:creator>
		<pubDate>Tue, 01 Aug 2006 18:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/#comment-2154</guid>
		<description>Why bother with target if you are going to use unobtrusive js to attach it?
You can simply find links with class=&quot;new-window&quot; and add the window.open and chrome code then cancel the default click behavior. Adding an invalid attribute the the anchor to do something that works fine another more valid way seems a waste of time. If you want to use target use target. If you can&#039;t or don&#039;t want to then do it the js way without adding invalid attributes to the DOM.</description>
		<content:encoded><![CDATA[<p>Why bother with target if you are going to use unobtrusive js to attach it?<br />
You can simply find links with class=&#8221;new-window&#8221; and add the window.open and chrome code then cancel the default click behavior. Adding an invalid attribute the the anchor to do something that works fine another more valid way seems a waste of time. If you want to use target use target. If you can&#8217;t or don&#8217;t want to then do it the js way without adding invalid attributes to the DOM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nat</title>
		<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/comment-page-1/#comment-2152</link>
		<dc:creator>Nat</dc:creator>
		<pubDate>Tue, 01 Aug 2006 05:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/#comment-2152</guid>
		<description>So, if you have valid XML and then use XSLT to transform it into an invalid HTML document ... the XML is &quot;invalid&quot;?</description>
		<content:encoded><![CDATA[<p>So, if you have valid XML and then use XSLT to transform it into an invalid HTML document &#8230; the XML is &#8220;invalid&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sébastien Guillon</title>
		<link>http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/comment-page-1/#comment-2146</link>
		<dc:creator>Sébastien Guillon</dc:creator>
		<pubDate>Sun, 30 Jul 2006 16:38:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/07/do-not-attach-target-through-script/#comment-2146</guid>
		<description>(Followed the link from Tantek&#039;s page)

The question is: Should browser accept to attach and work with a target attribute even if the document has a strict DOCTYPE? None that I know refuse to.
Can this be equated to a bug? Should browsers respect the DTD?

That would be a different web.</description>
		<content:encoded><![CDATA[<p>(Followed the link from Tantek&#8217;s page)</p>
<p>The question is: Should browser accept to attach and work with a target attribute even if the document has a strict DOCTYPE? None that I know refuse to.<br />
Can this be equated to a bug? Should browsers respect the DTD?</p>
<p>That would be a different web.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
