<?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: Linking To Non-Web Documents</title>
	<atom:link href="http://www.slicedbreaddesign.com/blog/index.php/2009/02/guidelines-for-linking-to-non-web-documents/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slicedbreaddesign.com/blog/index.php/2009/02/guidelines-for-linking-to-non-web-documents/</link>
	<description>an experience design blog</description>
	<lastBuildDate>Mon, 16 May 2011 06:16:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Marty DeAngelo</title>
		<link>http://www.slicedbreaddesign.com/blog/index.php/2009/02/guidelines-for-linking-to-non-web-documents/comment-page-1/#comment-68</link>
		<dc:creator>Marty DeAngelo</dc:creator>
		<pubDate>Fri, 29 May 2009 02:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.slicedbreaddesign.com/?p=241#comment-68</guid>
		<description>We run into this on a daily basis - and we have found that opening these in a new window (via target=&quot;_blank&quot;, usually) is the best experience.  However, in the case of PDFs particularly, you can only control this one of the three major aspects of the interaction; you CAN&#039;T control whether the user has their PDF reader app to open in the browser or the application itself, nor can you control their browser settings in regard to opening or preventing new windows/tabs.

Because of this, we found that the &#039;New Window&#039; icon can be confusing since user settings can override that.  And multiple icons were found to be confusing.  However, having the file type icon was found to be essential in aiding the user in understanding what type of file they are accessing.

I agree with your comment about forcing the dialog box - I think that it creates an extra step for the user that can be quite annoying.</description>
		<content:encoded><![CDATA[<p>We run into this on a daily basis &#8211; and we have found that opening these in a new window (via target=&#8221;_blank&#8221;, usually) is the best experience.  However, in the case of PDFs particularly, you can only control this one of the three major aspects of the interaction; you CAN&#8217;T control whether the user has their PDF reader app to open in the browser or the application itself, nor can you control their browser settings in regard to opening or preventing new windows/tabs.</p>
<p>Because of this, we found that the &#8216;New Window&#8217; icon can be confusing since user settings can override that.  And multiple icons were found to be confusing.  However, having the file type icon was found to be essential in aiding the user in understanding what type of file they are accessing.</p>
<p>I agree with your comment about forcing the dialog box &#8211; I think that it creates an extra step for the user that can be quite annoying.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

