<?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: New windows in xhtml strict</title>
	<atom:link href="http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 14:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Frederik</title>
		<link>http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/comment-page-1/#comment-144174</link>
		<dc:creator>Frederik</dc:creator>
		<pubDate>Wed, 30 May 2007 19:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2005/opening-links-in-new-windows-in-xhtml-strict/#comment-144174</guid>
		<description>W3C gives a more easy solution for exsample if you wish to use this on a link page. works very well&gt;

From te website of W3C:
Why was the target attribute removed from XHTML 1.1?

It wasn&#039;t. XHTML 1.0 comes in three versions: strict, transitional, and frameset. All three of these were deliberately kept as close as possible to HTML 4.01 as XML would allow. XHTML 1.1 is an updated version of XHTML 1.0 strict, and no version of HTML strict has ever included the target attribute. The other two versions, transitional and frameset, were not updated, because there was nothing to update. If you want to use the target attribute, use XHTML 1.0 transitional&quot;.</description>
		<content:encoded><![CDATA[<p>W3C gives a more easy solution for exsample if you wish to use this on a link page. works very well&gt;</p>
<p>From te website of W3C:<br />
Why was the target attribute removed from XHTML 1.1?</p>
<p>It wasn&#8217;t. XHTML 1.0 comes in three versions: strict, transitional, and frameset. All three of these were deliberately kept as close as possible to HTML 4.01 as XML would allow. XHTML 1.1 is an updated version of XHTML 1.0 strict, and no version of HTML strict has ever included the target attribute. The other two versions, transitional and frameset, were not updated, because there was nothing to update. If you want to use the target attribute, use XHTML 1.0 transitional&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Cherny</title>
		<link>http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/comment-page-1/#comment-41322</link>
		<dc:creator>Rob Cherny</dc:creator>
		<pubDate>Mon, 16 Oct 2006 12:49:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2005/opening-links-in-new-windows-in-xhtml-strict/#comment-41322</guid>
		<description>I don&#039;t think you&#039;re breaking any rules by dynamically inserting the &quot;target&quot; attribute here, as some have said. If it was hard coded, that&#039;d be one thing, but it&#039;s not.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think you&#8217;re breaking any rules by dynamically inserting the &#8220;target&#8221; attribute here, as some have said. If it was hard coded, that&#8217;d be one thing, but it&#8217;s not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/comment-page-1/#comment-1653</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Tue, 24 Jan 2006 20:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2005/opening-links-in-new-windows-in-xhtml-strict/#comment-1653</guid>
		<description>Yo &quot;Stephenrs&quot;  - got a link I can look at? </description>
		<content:encoded><![CDATA[<p>Yo &#8220;Stephenrs&#8221;  &#8211; got a link I can look at?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephenrs</title>
		<link>http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/comment-page-1/#comment-1651</link>
		<dc:creator>stephenrs</dc:creator>
		<pubDate>Tue, 24 Jan 2006 15:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2005/opening-links-in-new-windows-in-xhtml-strict/#comment-1651</guid>
		<description>hi bruce,

i&#039;m working on a new site that i&#039;m striving to make standards compliant. some of my links i would prefer to have open in a new window. i&#039;ve tried your solution using firefox 1.5, but the link still opens in the same window (tab). 

do you know of a way around this? are the days of forcing a new window to open behind us as standards compliant developers? is conventional wisdom telling us that opening new windows is just plain wrong?

also, with popups blocked in firefox the link does nothing at all when using the code above. i modified the bottom of your launchWindow function as follows to avoid having seemingly dead links:

var canOpen = window.open(objAnchor);
	if (!canOpen) document.location.href = objAnchor.getAttribute(&quot;href&quot;);

	return !canOpen;

thanks,

stephenrs</description>
		<content:encoded><![CDATA[<p>hi bruce,</p>
<p>i&#8217;m working on a new site that i&#8217;m striving to make standards compliant. some of my links i would prefer to have open in a new window. i&#8217;ve tried your solution using firefox 1.5, but the link still opens in the same window (tab). </p>
<p>do you know of a way around this? are the days of forcing a new window to open behind us as standards compliant developers? is conventional wisdom telling us that opening new windows is just plain wrong?</p>
<p>also, with popups blocked in firefox the link does nothing at all when using the code above. i modified the bottom of your launchWindow function as follows to avoid having seemingly dead links:</p>
<p>var canOpen = window.open(objAnchor);<br />
	if (!canOpen) document.location.href = objAnchor.getAttribute(&#8220;href&#8221;);</p>
<p>	return !canOpen;</p>
<p>thanks,</p>
<p>stephenrs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Neubauer</title>
		<link>http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/comment-page-1/#comment-653</link>
		<dc:creator>Alan Neubauer</dc:creator>
		<pubDate>Tue, 22 Nov 2005 21:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2005/opening-links-in-new-windows-in-xhtml-strict/#comment-653</guid>
		<description>OK so I see there is much debate over this whole thing.  Unfortunately I do not have the luxury of choosing.  Add to that the fact that I am NOT a web person -- but really a router person pretending to do web code.  I thought I would do a favor for some of our legal staff and create a page for Jury Instructions that would be accessable by the general public.  The content is a bunch of .rtf files that IE opens in a new page  ( I happily used the _blank target).  Unfortunately, the 26% of the world population that uses FF or NN get the blank page described earlier.  I have performed a browser identification earlier in my page and used that information in some JS in the body of my page.  Is there a way to build a tag that will behave differently based on the different browser type.</description>
		<content:encoded><![CDATA[<p>OK so I see there is much debate over this whole thing.  Unfortunately I do not have the luxury of choosing.  Add to that the fact that I am NOT a web person &#8212; but really a router person pretending to do web code.  I thought I would do a favor for some of our legal staff and create a page for Jury Instructions that would be accessable by the general public.  The content is a bunch of .rtf files that IE opens in a new page  ( I happily used the _blank target).  Unfortunately, the 26% of the world population that uses FF or NN get the blank page described earlier.  I have performed a browser identification earlier in my page and used that information in some JS in the body of my page.  Is there a way to build a tag that will behave differently based on the different browser type.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schmidt Eckhart</title>
		<link>http://www.brucelawson.co.uk/2005/opening-links-in-new-windows-in-xhtml-strict/comment-page-1/#comment-561</link>
		<dc:creator>Schmidt Eckhart</dc:creator>
		<pubDate>Wed, 09 Nov 2005 11:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2005/opening-links-in-new-windows-in-xhtml-strict/#comment-561</guid>
		<description>&lt;strong&gt;Bruce Lawson&#8217;s personal site &#160; : New windows in xhtml strict&lt;/strong&gt;

Bruce Lawson&#8217;s p...</description>
		<content:encoded><![CDATA[<p><strong>Bruce Lawson&#8217;s personal site &nbsp; : New windows in xhtml strict</strong></p>
<p>Bruce Lawson&#8217;s p&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

