<?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: W3C Valid Replacement for target=&#8221;_blank&#8221;</title>
	<atom:link href="http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html</link>
	<description>A Whole Lot of AJAX!</description>
	<lastBuildDate>Tue, 10 Jan 2012 16:11:09 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Me</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-2171</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Wed, 07 Sep 2011 10:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-2171</guid>
		<description>Actually all you guys do is trying to trick the w3c-validator with js. I don&#039;t think any of this is really necessarry, since every browser nowadays can still interpret the target-tag. I think W3C is generally a good help to keep your html clean, but you should not let it force you to come up with some nasty workarounds. Also, almost no big company website in the www is w3c-conform, so who cares?

Same goes for the autocomplete-tag on password-inputs. Absolutely great tag, but one &quot;doesn&#039;t dare to use it, because w3c-validator will get mad, buhu&quot;.</description>
		<content:encoded><![CDATA[<p>Actually all you guys do is trying to trick the w3c-validator with js. I don&#8217;t think any of this is really necessarry, since every browser nowadays can still interpret the target-tag. I think W3C is generally a good help to keep your html clean, but you should not let it force you to come up with some nasty workarounds. Also, almost no big company website in the www is w3c-conform, so who cares?</p>
<p>Same goes for the autocomplete-tag on password-inputs. Absolutely great tag, but one &#8220;doesn&#8217;t dare to use it, because w3c-validator will get mad, buhu&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Tinker</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-1979</link>
		<dc:creator>Tom Tinker</dc:creator>
		<pubDate>Mon, 22 Aug 2011 13:37:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-1979</guid>
		<description>But the much shorter onclick=&quot;target=&#039;_blank&#039;;&quot;
passes the W3C online validator, works just as well, and is a lot simpler...</description>
		<content:encoded><![CDATA[<p>But the much shorter onclick=&#8221;target=&#8217;_blank&#8217;;&#8221;<br />
passes the W3C online validator, works just as well, and is a lot simpler&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Biggebass</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-1088</link>
		<dc:creator>Biggebass</dc:creator>
		<pubDate>Mon, 18 Apr 2011 10:35:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-1088</guid>
		<description>I tried but your demo button but it did not work.

My problem is that I am using IE9 32-bit in Win7 and target=_blank and the demo button result in the same way: A new tab is created but it is completely blank (no content at all). It&#039;s valid for all appempt to open a new tab/window - but only in the 32-bit version.</description>
		<content:encoded><![CDATA[<p>I tried but your demo button but it did not work.</p>
<p>My problem is that I am using IE9 32-bit in Win7 and target=_blank and the demo button result in the same way: A new tab is created but it is completely blank (no content at all). It&#8217;s valid for all appempt to open a new tab/window &#8211; but only in the 32-bit version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren - ajaxBlender</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-353</link>
		<dc:creator>Darren - ajaxBlender</dc:creator>
		<pubDate>Wed, 10 Mar 2010 16:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-353</guid>
		<description>Jonny, our testing shows that the script (and the above mod) are working correctly with a lightbox add-on. If you provide your code, we would be happy to troubleshoot it. Either post here or email us at support@. Thanks!</description>
		<content:encoded><![CDATA[<p>Jonny, our testing shows that the script (and the above mod) are working correctly with a lightbox add-on. If you provide your code, we would be happy to troubleshoot it. Either post here or email us at support@. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonny</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-333</link>
		<dc:creator>Jonny</dc:creator>
		<pubDate>Wed, 10 Mar 2010 05:13:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-333</guid>
		<description>This doesn&#039;t play nice with Lightbox... any suggestions?</description>
		<content:encoded><![CDATA[<p>This doesn&#8217;t play nice with Lightbox&#8230; any suggestions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren - ajaxBlender</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-75</link>
		<dc:creator>Darren - ajaxBlender</dc:creator>
		<pubDate>Mon, 11 Jan 2010 14:22:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-75</guid>
		<description>Here is a quick mod to maximize the new window for the 2nd. (It will not work with the first solution though.):

     $(document).ready(function(){
          $(&#039;A[rel=&quot;_blank&quot;]&#039;).click(function(){
               var wndHandle = window.open($(this).attr(&#039;href&#039;));
               wndHandle.moveTo(0, 0);
               wndHandle.resizeTo(screen.width, screen.height);
               return false;
          });
     });</description>
		<content:encoded><![CDATA[<p>Here is a quick mod to maximize the new window for the 2nd. (It will not work with the first solution though.):</p>
<p>     $(document).ready(function(){<br />
          $(&#8217;A[rel="_blank"]&#8216;).click(function(){<br />
               var wndHandle = window.open($(this).attr(&#8217;href&#8217;));<br />
               wndHandle.moveTo(0, 0);<br />
               wndHandle.resizeTo(screen.width, screen.height);<br />
               return false;<br />
          });<br />
     });</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Albert</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-74</link>
		<dc:creator>Albert</dc:creator>
		<pubDate>Tue, 05 Jan 2010 07:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-74</guid>
		<description>Thanks. How to maximize the new window when submit the page through JS Code.</description>
		<content:encoded><![CDATA[<p>Thanks. How to maximize the new window when submit the page through JS Code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.ajaxblender.com/open-links-new-window-w3c-valid-target-blank.html/comment-page-1#comment-73</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 31 Dec 2009 16:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxblender.com/?p=1074#comment-73</guid>
		<description>Thanks for the tutorial. I was looking hard for a SEO friendly way to do this. thanks guys!</description>
		<content:encoded><![CDATA[<p>Thanks for the tutorial. I was looking hard for a SEO friendly way to do this. thanks guys!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

