<?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: Browser Width: A Response</title>
	<atom:link href="http://www.jasondunn.com/browser-width-a-response-185/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jasondunn.com/browser-width-a-response-185</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 12:28:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Jason Dunn</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-182</link>
		<dc:creator>Jason Dunn</dc:creator>
		<pubDate>Thu, 01 Feb 2007 22:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-182</guid>
		<description><![CDATA[&lt;I&gt;…design a site so that it can be viewed at 1024×768, filling part of the screen on a hi res monitor, or full screen on a hi res monitor, for users such as me :)&lt;/I&gt;

And that&#039;s the classic question: do I allow my site design to be warped into a wide, unreadable mess? Or do I fix the width to a reasonable compromise and lock in the design? Or do I provide a CSS switch to allow people to do what they want? There&#039;s no right or wrong answer IMO. I have sites that are fixed width, and sites that are variable.

&lt;I&gt;Also with regards to the above, I’d be really surprised if ‘multiple windows on the display at once’ was as common a usage scenario as you think?&lt;/I&gt;

A great question - based on how I work, and how I&#039;ve seen other people work, the higher the resolution, the higher the chance of people using smaller, multiple windows. I wish log file software could track THIS. ;-)]]></description>
		<content:encoded><![CDATA[<p><i>…design a site so that it can be viewed at 1024×768, filling part of the screen on a hi res monitor, or full screen on a hi res monitor, for users such as me <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </i></p>
<p>And that&#8217;s the classic question: do I allow my site design to be warped into a wide, unreadable mess? Or do I fix the width to a reasonable compromise and lock in the design? Or do I provide a CSS switch to allow people to do what they want? There&#8217;s no right or wrong answer IMO. I have sites that are fixed width, and sites that are variable.</p>
<p><i>Also with regards to the above, I’d be really surprised if ‘multiple windows on the display at once’ was as common a usage scenario as you think?</i></p>
<p>A great question &#8211; based on how I work, and how I&#8217;ve seen other people work, the higher the resolution, the higher the chance of people using smaller, multiple windows. I wish log file software could track THIS. <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulAtMoDaCo</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-180</link>
		<dc:creator>PaulAtMoDaCo</dc:creator>
		<pubDate>Thu, 01 Feb 2007 21:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-180</guid>
		<description><![CDATA[Edit: Just tried Sizer again and it IS working on Vista now (after installing as an admin).

Worth checking out: http://www.brianapps.net/sizer.html

P]]></description>
		<content:encoded><![CDATA[<p>Edit: Just tried Sizer again and it IS working on Vista now (after installing as an admin).</p>
<p>Worth checking out: <a href="http://www.brianapps.net/sizer.html" rel="nofollow">http://www.brianapps.net/sizer.html</a></p>
<p>P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulAtMoDaCo</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-179</link>
		<dc:creator>PaulAtMoDaCo</dc:creator>
		<pubDate>Thu, 01 Feb 2007 21:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-179</guid>
		<description><![CDATA[Filip:

&quot;And if Paul is reading this, umm… trying to read this with no filled screen effect, then he should really try another web browser!&quot;

How do u mean?

P]]></description>
		<content:encoded><![CDATA[<p>Filip:</p>
<p>&#8220;And if Paul is reading this, umm… trying to read this with no filled screen effect, then he should really try another web browser!&#8221;</p>
<p>How do u mean?</p>
<p>P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulAtMoDaCo</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-178</link>
		<dc:creator>PaulAtMoDaCo</dc:creator>
		<pubDate>Thu, 01 Feb 2007 21:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-178</guid>
		<description><![CDATA[First things first... my blog (PaulOBrien.net) was whipped up quick smart using the standard Drupal skin, so I make no apologies for how it currently looks. I should verify posted pictures look right in 1024x768 res (which is the width I deem as minimum supported), however I guess i&#039;ve got lazy since I switched to Vista and discovered the excellent &#039;Sizer&#039; (http://www.brianapps.net/sizer.html) didn&#039;t work.

With regards to MoDaCo, it (should) display correctly on 1024x768 and on wide screens - as far as I am aware - so that users effectively have the choice... so that&#039;s my point basically...

...design a site so that it can be viewed at 1024x768, filling part of the screen on a hi res monitor, or full screen on a hi res monitor, for users such as me :)

Also with regards to the above, I&#039;d be really surprised if &#039;multiple windows on the display at once&#039; was as common a usage scenario as you think?

P]]></description>
		<content:encoded><![CDATA[<p>First things first&#8230; my blog (PaulOBrien.net) was whipped up quick smart using the standard Drupal skin, so I make no apologies for how it currently looks. I should verify posted pictures look right in 1024&#215;768 res (which is the width I deem as minimum supported), however I guess i&#8217;ve got lazy since I switched to Vista and discovered the excellent &#8216;Sizer&#8217; (<a href="http://www.brianapps.net/sizer.html" rel="nofollow">http://www.brianapps.net/sizer.html</a>) didn&#8217;t work.</p>
<p>With regards to MoDaCo, it (should) display correctly on 1024&#215;768 and on wide screens &#8211; as far as I am aware &#8211; so that users effectively have the choice&#8230; so that&#8217;s my point basically&#8230;</p>
<p>&#8230;design a site so that it can be viewed at 1024&#215;768, filling part of the screen on a hi res monitor, or full screen on a hi res monitor, for users such as me <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Also with regards to the above, I&#8217;d be really surprised if &#8216;multiple windows on the display at once&#8217; was as common a usage scenario as you think?</p>
<p>P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Dunn</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-176</link>
		<dc:creator>Jason Dunn</dc:creator>
		<pubDate>Thu, 01 Feb 2007 14:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-176</guid>
		<description><![CDATA[&lt;I&gt;&quot;Don’t we embed ads in the full-content feeds?&quot;&lt;/I&gt;

We do, but there aren&#039;t enough RSS ads coming from Feedburner to put one in every feed, so not every piece of content is monetized. Also, a single RSS ad can&#039;t equal the ads on the rest of the site.]]></description>
		<content:encoded><![CDATA[<p><i>&#8220;Don’t we embed ads in the full-content feeds?&#8221;</i></p>
<p>We do, but there aren&#8217;t enough RSS ads coming from Feedburner to put one in every feed, so not every piece of content is monetized. Also, a single RSS ad can&#8217;t equal the ads on the rest of the site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janak Parekh</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-175</link>
		<dc:creator>Janak Parekh</dc:creator>
		<pubDate>Thu, 01 Feb 2007 02:57:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-175</guid>
		<description><![CDATA[&lt;i&gt;&quot;As a professional with a news site that has ads, that comment makes me weep. ;-)&quot;&lt;/i&gt;

Don&#039;t we embed ads in the full-content feeds? :)]]></description>
		<content:encoded><![CDATA[<p><i>&#8220;As a professional with a news site that has ads, that comment makes me weep. <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> &#8221;</i></p>
<p>Don&#8217;t we embed ads in the full-content feeds? <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Dunn</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-173</link>
		<dc:creator>Jason Dunn</dc:creator>
		<pubDate>Wed, 31 Jan 2007 20:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-173</guid>
		<description><![CDATA[I should point out that I&#039;m well aware of the irony of a post about readability from a guy who has a blog with white text on a red background that isn&#039;t super easy to read. :lol:]]></description>
		<content:encoded><![CDATA[<p>I should point out that I&#8217;m well aware of the irony of a post about readability from a guy who has a blog with white text on a red background that isn&#8217;t super easy to read. <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_lol.gif' alt=':lol:' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Filip Norrgård</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-171</link>
		<dc:creator>Filip Norrgård</dc:creator>
		<pubDate>Wed, 31 Jan 2007 20:02:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-171</guid>
		<description><![CDATA[Heh, I think my blog/site must also look ugly on higher resolutions, although I fine-tuned it to my 15 inch screen on a 1680 x 1050 resolution. I&#039;ve tried making the site a bit more readable, and I guess the measure of readability is YMMV. ;)

The Modaco site doesn&#039;t look that nice in the screenshot you took, and fixed widths might be better/worse depending on which browser you use. In this case, some extra column of ads, or relevant content, would fit just fine. The main problem is probably that it can be tricky (?) to implement.

There are certain sites that offer the possibility of chaning the CSS by clicking a button, and that should be the place to leave an option for anyone running ultra-high resolutions. The option I tend to use with width flowing sites is zooming in using the browser and turn on &quot;fit to width&quot;. (The bonus is that reading is a lot more easier on the eyes) &lt;a href=&quot;http://www.filips.net/wp/wp-content/uploads/screenshotofascreenshot.png&quot; rel=&quot;nofollow&quot;&gt;Here&#039;s a screenshot&lt;/a&gt; of how I like to zoom in. :)

And if Paul is reading this, umm... &lt;i&gt;trying&lt;/i&gt; to read this with no filled screen effect, then he should really try another web browser! :D]]></description>
		<content:encoded><![CDATA[<p>Heh, I think my blog/site must also look ugly on higher resolutions, although I fine-tuned it to my 15 inch screen on a 1680 x 1050 resolution. I&#8217;ve tried making the site a bit more readable, and I guess the measure of readability is YMMV. <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>The Modaco site doesn&#8217;t look that nice in the screenshot you took, and fixed widths might be better/worse depending on which browser you use. In this case, some extra column of ads, or relevant content, would fit just fine. The main problem is probably that it can be tricky (?) to implement.</p>
<p>There are certain sites that offer the possibility of chaning the CSS by clicking a button, and that should be the place to leave an option for anyone running ultra-high resolutions. The option I tend to use with width flowing sites is zooming in using the browser and turn on &#8220;fit to width&#8221;. (The bonus is that reading is a lot more easier on the eyes) <a href="http://www.filips.net/wp/wp-content/uploads/screenshotofascreenshot.png" rel="nofollow">Here&#8217;s a screenshot</a> of how I like to zoom in. <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>And if Paul is reading this, umm&#8230; <i>trying</i> to read this with no filled screen effect, then he should really try another web browser! <img src='http://www.jasondunn.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Dunn</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-168</link>
		<dc:creator>Jason Dunn</dc:creator>
		<pubDate>Tue, 30 Jan 2007 22:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-168</guid>
		<description><![CDATA[Yeah, the 1024 limit is where I think a fair &quot;middle ground&quot; resolution is for Web sites. Our template for Zune Thoughts is 1000 pixels wide (give or take) and I always chuckle when I come across Web sites that are designed for 1200+ pixels in width.]]></description>
		<content:encoded><![CDATA[<p>Yeah, the 1024 limit is where I think a fair &#8220;middle ground&#8221; resolution is for Web sites. Our template for Zune Thoughts is 1000 pixels wide (give or take) and I always chuckle when I come across Web sites that are designed for 1200+ pixels in width.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oilman</title>
		<link>http://www.jasondunn.com/browser-width-a-response-185/comment-page-1#comment-167</link>
		<dc:creator>oilman</dc:creator>
		<pubDate>Tue, 30 Jan 2007 18:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasondunn.com/browser-width-a-response-185#comment-167</guid>
		<description><![CDATA[It&#039;s quite interesting to see your stats showing that much high resolution readership but I guess it&#039;s really tied to your audience. You run technology enthusiast sites so it&#039;s not suprising to see 12% above 1600. I am privy to the stats of a several top etailer sites and I can assure you that the general public by and large is still hugely in favor of 800x600 and 1024x768 and just barely edging into larger displays. 

I also agree that too wide is too hard to read. The eye doesn&#039;t track back to the next line easily when you&#039;re having to scan back over the width of a 24&quot; widescreen. I use dual 20&quot; widescreens here and I rarely run anything maximized to that resolution.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s quite interesting to see your stats showing that much high resolution readership but I guess it&#8217;s really tied to your audience. You run technology enthusiast sites so it&#8217;s not suprising to see 12% above 1600. I am privy to the stats of a several top etailer sites and I can assure you that the general public by and large is still hugely in favor of 800&#215;600 and 1024&#215;768 and just barely edging into larger displays. </p>
<p>I also agree that too wide is too hard to read. The eye doesn&#8217;t track back to the next line easily when you&#8217;re having to scan back over the width of a 24&#8243; widescreen. I use dual 20&#8243; widescreens here and I rarely run anything maximized to that resolution.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
