<?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: Design for Browser Size &#8212; Not Screen Size</title>
	<atom:link href="http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/feed/" rel="self" type="application/rss+xml" />
	<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/</link>
	<description>Instant Usability &#38; Web Standards</description>
	<lastBuildDate>Sat, 13 Mar 2010 05:37:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Usability: Browser Size und Seitenlayout &#187; melon&#124;media Internetagentur</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-493219</link>
		<dc:creator>Usability: Browser Size und Seitenlayout &#187; melon&#124;media Internetagentur</dc:creator>
		<pubDate>Sat, 27 Feb 2010 14:35:18 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-493219</guid>
		<description>[...] Rønn-Jensen formulierte diese wichtige Feststellung in seinem Artikel &#8220;Design for Browser Size — Not Screen Size&#8220;. Ferner verdeutlicht er, dass für die Gestaltung einer Website die Bildschirmauflösung [...]</description>
		<content:encoded><![CDATA[<p>[...] Rønn-Jensen formulierte diese wichtige Feststellung in seinem Artikel &#8220;Design for Browser Size — Not Screen Size&#8220;. Ferner verdeutlicht er, dass für die Gestaltung einer Website die Bildschirmauflösung [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew Clarke</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-490351</link>
		<dc:creator>Drew Clarke</dc:creator>
		<pubDate>Fri, 23 Oct 2009 12:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-490351</guid>
		<description>Is there a chance that this very useful article can be updated and mobile screens included please?

Thanks</description>
		<content:encoded><![CDATA[<p>Is there a chance that this very useful article can be updated and mobile screens included please?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-09-15 &#171; sySolution</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-489158</link>
		<dc:creator>links for 2009-09-15 &#171; sySolution</dc:creator>
		<pubDate>Tue, 15 Sep 2009 15:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-489158</guid>
		<description>[...] justaddwater.dk &#124; Design for Browser Size — Not Screen Size (tags: browser resolution) [...]</description>
		<content:encoded><![CDATA[<p>[...] justaddwater.dk | Design for Browser Size — Not Screen Size (tags: browser resolution) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thoughts on design &#124; tdhedengren</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-423408</link>
		<dc:creator>Thoughts on design &#124; tdhedengren</dc:creator>
		<pubDate>Thu, 12 Jun 2008 16:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-423408</guid>
		<description>[...] derived from three great posts, from usability guru Jakob Nielsen and Jesper Ronn-Jensen’s two recent posts on the [...]</description>
		<content:encoded><![CDATA[<p>[...] derived from three great posts, from usability guru Jakob Nielsen and Jesper Ronn-Jensen’s two recent posts on the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erick S.</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-390149</link>
		<dc:creator>Erick S.</dc:creator>
		<pubDate>Fri, 18 Jan 2008 13:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-390149</guid>
		<description>Sometimes I use the &#039;webdeveloper toolbar&#039; within Firefox, but quickly close this again after usage, cause the &#039;Navigation Toolbar&#039; and the &#039;Bookmarks Toolbar&#039; allready take up a lot of space.

Also it doesn&#039;t seem possible to remove the bar that holds the tabs...Or is there?

Everybody has got something with their browserwindow, of course also things not mentioned here, and it is impossible to keep everybody happy.

Some just will have to scroll...Others will just have to increase textsize to their likings...And some should just buy a monitor of this time.

...I will continue my exporations with 1024x768 in mind for the time being.

(thanks Mike!)</description>
		<content:encoded><![CDATA[<p>Sometimes I use the &#8216;webdeveloper toolbar&#8217; within Firefox, but quickly close this again after usage, cause the &#8216;Navigation Toolbar&#8217; and the &#8216;Bookmarks Toolbar&#8217; allready take up a lot of space.</p>
<p>Also it doesn&#8217;t seem possible to remove the bar that holds the tabs&#8230;Or is there?</p>
<p>Everybody has got something with their browserwindow, of course also things not mentioned here, and it is impossible to keep everybody happy.</p>
<p>Some just will have to scroll&#8230;Others will just have to increase textsize to their likings&#8230;And some should just buy a monitor of this time.</p>
<p>&#8230;I will continue my exporations with 1024&#215;768 in mind for the time being.</p>
<p>(thanks Mike!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike sherwin</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-390141</link>
		<dc:creator>mike sherwin</dc:creator>
		<pubDate>Fri, 18 Jan 2008 11:32:17 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-390141</guid>
		<description>Hi Erick

No standard way as such as everyone will have different browser set ups. I think the solution is to work well within 1024*768 e.g. pixels wide and if aiming to fit full height with no vertical scroll on a maximised 1024*768 window then say 570 pixels high.

As folk mention above it&#039;s difficult to call exactly due to monitors, browser set ups. I simply aim to work well within 1024*768. It may mean some white space but I kind of like that...</description>
		<content:encoded><![CDATA[<p>Hi Erick</p>
<p>No standard way as such as everyone will have different browser set ups. I think the solution is to work well within 1024*768 e.g. pixels wide and if aiming to fit full height with no vertical scroll on a maximised 1024*768 window then say 570 pixels high.</p>
<p>As folk mention above it&#8217;s difficult to call exactly due to monitors, browser set ups. I simply aim to work well within 1024*768. It may mean some white space but I kind of like that&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erick S.</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-390054</link>
		<dc:creator>Erick S.</dc:creator>
		<pubDate>Thu, 17 Jan 2008 22:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-390054</guid>
		<description>Mike,
What exactly do you mean with the following:
&quot;reductions for toolbars etc&quot;

Is there a standard way to keep this in mind?</description>
		<content:encoded><![CDATA[<p>Mike,<br />
What exactly do you mean with the following:<br />
&#8220;reductions for toolbars etc&#8221;</p>
<p>Is there a standard way to keep this in mind?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike sherwin</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-390039</link>
		<dc:creator>mike sherwin</dc:creator>
		<pubDate>Thu, 17 Jan 2008 20:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-390039</guid>
		<description>Agree Erick.

Sure 1024*768 will be the next 800*600 but nothing ever stays still, colour was the new black and white, high defintion will be the next colour.

Everything changes ;-))</description>
		<content:encoded><![CDATA[<p>Agree Erick.</p>
<p>Sure 1024*768 will be the next 800*600 but nothing ever stays still, colour was the new black and white, high defintion will be the next colour.</p>
<p>Everything changes ;-))</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erick S.</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-389738</link>
		<dc:creator>Erick S.</dc:creator>
		<pubDate>Tue, 15 Jan 2008 19:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-389738</guid>
		<description>The people using 800x600 must realize that this is small, so they have to suffer the consequences. I don&#039;t really care about this resolution. 

But when a website designed for a 1024x768 resolution is viewed on a monitor with 1280x1024 it looks like the website is very small...

And at the moment everybody I know has bought a new &#039;flatscreen&#039; or is soon going to...And these all have bigger resolutions than 1024x768. So I think 1024x768 soon will be the next 800x600...And when we reach that point in time the discussion will continue with a whole range of new resolutions.

Ah well...It keeps me of the streets...</description>
		<content:encoded><![CDATA[<p>The people using 800&#215;600 must realize that this is small, so they have to suffer the consequences. I don&#8217;t really care about this resolution. </p>
<p>But when a website designed for a 1024&#215;768 resolution is viewed on a monitor with 1280&#215;1024 it looks like the website is very small&#8230;</p>
<p>And at the moment everybody I know has bought a new &#8216;flatscreen&#8217; or is soon going to&#8230;And these all have bigger resolutions than 1024&#215;768. So I think 1024&#215;768 soon will be the next 800&#215;600&#8230;And when we reach that point in time the discussion will continue with a whole range of new resolutions.</p>
<p>Ah well&#8230;It keeps me of the streets&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike sherwin</title>
		<link>http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/comment-page-1/#comment-389735</link>
		<dc:creator>mike sherwin</dc:creator>
		<pubDate>Tue, 15 Jan 2008 19:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/08/17/design-for-browser-size-not-screen-size/#comment-389735</guid>
		<description>Liquid layouts are all well and good for blogs, forums etc but from an aesthetic/design perspective, as well as a readibility perspective (e.g. see comments re. long line length on Macs above) they can be tricky. 

As mentioned max-width and height aren&#039;t fully supported by browsers so as yet that is not a solution.

Personally I opt for a 1024*768 FIXED  (with reductions for toolbars etc) display. Used to work in 800*600 but my site logs are showing under 1% of users still using 800*600.

As for mobile devices I&#039;m in favour of feeding them a different stylesheet. It&#039;s more work sure but I like to think it avoids everything being homogenous and allows some creativity.

What Nielson misses is the the aesthetic design principle - in short this means his &quot;users&quot; will form a relationship with designs that are aesthetically pleasing. Sure it may mean a little extra work i.e. one click to maximise or enlarge the browser but contrary to what &#039;user testing&#039; may say (being flippant - ask people to whinge and they will) people really don&#039;t mind this.

Horse for courses, there as yet is no perfect solution. 

Certainly games  designers/programmers don&#039;t avoid High Definition for the 360 and PS360 just because the Wii and PSP etc aren&#039;t in HD, nope they rewrite the code. Film makers make films in widescreen though some TV viewers still have 4*3.

And of course as mentioned there&#039;s images in a liquid layout ...these remain fixed width..so the user still has to scroll horizontally to view. 

Still having said the notion of building liquid for 800*600 upto say 1280*1024 is reasonable. One could then assume most users will view in 1024*768 (say approx. 80%) and optimise for this. The problem arises if the aesthetic design is compromised at higher resolution, or even for the few still with 800*600.</description>
		<content:encoded><![CDATA[<p>Liquid layouts are all well and good for blogs, forums etc but from an aesthetic/design perspective, as well as a readibility perspective (e.g. see comments re. long line length on Macs above) they can be tricky. </p>
<p>As mentioned max-width and height aren&#8217;t fully supported by browsers so as yet that is not a solution.</p>
<p>Personally I opt for a 1024*768 FIXED  (with reductions for toolbars etc) display. Used to work in 800*600 but my site logs are showing under 1% of users still using 800*600.</p>
<p>As for mobile devices I&#8217;m in favour of feeding them a different stylesheet. It&#8217;s more work sure but I like to think it avoids everything being homogenous and allows some creativity.</p>
<p>What Nielson misses is the the aesthetic design principle &#8211; in short this means his &#8220;users&#8221; will form a relationship with designs that are aesthetically pleasing. Sure it may mean a little extra work i.e. one click to maximise or enlarge the browser but contrary to what &#8216;user testing&#8217; may say (being flippant &#8211; ask people to whinge and they will) people really don&#8217;t mind this.</p>
<p>Horse for courses, there as yet is no perfect solution. </p>
<p>Certainly games  designers/programmers don&#8217;t avoid High Definition for the 360 and PS360 just because the Wii and PSP etc aren&#8217;t in HD, nope they rewrite the code. Film makers make films in widescreen though some TV viewers still have 4*3.</p>
<p>And of course as mentioned there&#8217;s images in a liquid layout &#8230;these remain fixed width..so the user still has to scroll horizontally to view. </p>
<p>Still having said the notion of building liquid for 800*600 upto say 1280*1024 is reasonable. One could then assume most users will view in 1024*768 (say approx. 80%) and optimise for this. The problem arises if the aesthetic design is compromised at higher resolution, or even for the few still with 800*600.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
