<?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: target=&#8221;_blank&#8221; XHTML replacement.</title>
	<atom:link href="http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 09:37:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: archatas</title>
		<link>http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/comment-page-1/#comment-18022</link>
		<dc:creator>archatas</dc:creator>
		<pubDate>Tue, 08 Jun 2010 15:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.no-margin-for-errors.com/?p=288#comment-18022</guid>
		<description>I would rather use window.open() instead of .attr(‘target’,&#039;_blank’). I like the idea to use rel=&quot;external&quot;, but sometimes it might be useful to use class=&quot;external&quot; to show an icon next to the link.

BTW, popup blockers block those popups which are opened by other events than click.</description>
		<content:encoded><![CDATA[<p>I would rather use window.open() instead of .attr(‘target’,&#8217;_blank’). I like the idea to use rel=&#8221;external&#8221;, but sometimes it might be useful to use class=&#8221;external&#8221; to show an icon next to the link.</p>
<p>BTW, popup blockers block those popups which are opened by other events than click.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Validar target="_blank" en la W3C &#124; Puente Cromático</title>
		<link>http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/comment-page-1/#comment-12738</link>
		<dc:creator>Validar target="_blank" en la W3C &#124; Puente Cromático</dc:creator>
		<pubDate>Sat, 10 Apr 2010 19:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.no-margin-for-errors.com/?p=288#comment-12738</guid>
		<description>[...] No margin for errors   Te gustó este post? Compartelo en tus redes sociales [...]</description>
		<content:encoded><![CDATA[<p>[...] No margin for errors   Te gustó este post? Compartelo en tus redes sociales [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JFFortier</title>
		<link>http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/comment-page-1/#comment-4272</link>
		<dc:creator>JFFortier</dc:creator>
		<pubDate>Fri, 18 Dec 2009 18:44:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.no-margin-for-errors.com/?p=288#comment-4272</guid>
		<description>I never had any problems with pop-up blockers but I must admit I never did an extensive testing on all of them. However we can easily replace the bind() by .attr(&#039;target&#039;,&#039;_blank&#039;). Actually, I&#039;ll do that for now on.</description>
		<content:encoded><![CDATA[<p>I never had any problems with pop-up blockers but I must admit I never did an extensive testing on all of them. However we can easily replace the bind() by .attr(&#8216;target&#8217;,'_blank&#8217;). Actually, I&#8217;ll do that for now on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephane</title>
		<link>http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/comment-page-1/#comment-4130</link>
		<dc:creator>Stephane</dc:creator>
		<pubDate>Thu, 17 Dec 2009 13:37:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.no-margin-for-errors.com/?p=288#comment-4130</guid>
		<description>@JFFortier: That&#039;s a very clever technique. Never thought of it.

The only thing, I always fear using window.open thinking browsers might trigger this as being an unwanted popup, but never got around testing it everywhere. I guess you never had problem with it?</description>
		<content:encoded><![CDATA[<p>@JFFortier: That&#8217;s a very clever technique. Never thought of it.</p>
<p>The only thing, I always fear using window.open thinking browsers might trigger this as being an unwanted popup, but never got around testing it everywhere. I guess you never had problem with it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JFFortier</title>
		<link>http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/comment-page-1/#comment-4085</link>
		<dc:creator>JFFortier</dc:creator>
		<pubDate>Thu, 17 Dec 2009 04:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.no-margin-for-errors.com/?p=288#comment-4085</guid>
		<description>I&#039;m not a big fan of opening pages in new windows. Most browsers allow me to control with a right click or a keyboard key where I want a link to open (either the same page, a new tab or a new window). Because most users don&#039;t know about this feature, I feel obligated to code the opening of an external url in a new window so that they don&#039;t quit my site. So using a technique like this is perfect; valid, semantic and clean. However, adding rel=&quot;external&quot; to all external links can be a lot of work and might not be possible using a cms wysiwyg. I use a similar technique: 

var allowedDomains = [location.hostname, &quot;myotherwebsite.com&quot;];
$(&quot;a[href^=http]:not(.internal)&quot;)
.filter(function(el){
	for ( var i=0; i -1 )
		return false;
	}
	return true;
})
.bind(&quot;click&quot;, function(){ return !window.open(this.href); });</description>
		<content:encoded><![CDATA[<p>I&#8217;m not a big fan of opening pages in new windows. Most browsers allow me to control with a right click or a keyboard key where I want a link to open (either the same page, a new tab or a new window). Because most users don&#8217;t know about this feature, I feel obligated to code the opening of an external url in a new window so that they don&#8217;t quit my site. So using a technique like this is perfect; valid, semantic and clean. However, adding rel=&#8221;external&#8221; to all external links can be a lot of work and might not be possible using a cms wysiwyg. I use a similar technique: </p>
<p>var allowedDomains = [location.hostname, "myotherwebsite.com"];<br />
$(&#8220;a[href^=http]:not(.internal)&#8221;)<br />
.filter(function(el){<br />
	for ( var i=0; i -1 )<br />
		return false;<br />
	}<br />
	return true;<br />
})<br />
.bind(&#8220;click&#8221;, function(){ return !window.open(this.href); });</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal</title>
		<link>http://www.no-margin-for-errors.com/blog/2009/12/16/target_blank-xhtml-replacement/comment-page-1/#comment-4033</link>
		<dc:creator>Michal</dc:creator>
		<pubDate>Wed, 16 Dec 2009 18:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.no-margin-for-errors.com/?p=288#comment-4033</guid>
		<description>It`s a workaround to pass the validation. I`m always against such practices.

I use js to open new window and close it when needed. JS offers methods to do so and in my opinion there so no need to base on target deprecated attribute.</description>
		<content:encoded><![CDATA[<p>It`s a workaround to pass the validation. I`m always against such practices.</p>
<p>I use js to open new window and close it when needed. JS offers methods to do so and in my opinion there so no need to base on target deprecated attribute.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

