<?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: Elastic or not?</title>
	<atom:link href="http://nickcowie.com/2008/elastic-or-not/feed/" rel="self" type="application/rss+xml" />
	<link>http://nickcowie.com/2008/elastic-or-not/</link>
	<description>Web standards, accessibility  and such like with a bias toward  Government web sites</description>
	<lastBuildDate>Mon, 21 May 2012 14:57:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: RE Mogul</title>
		<link>http://nickcowie.com/2008/elastic-or-not/comment-page-1/#comment-37367</link>
		<dc:creator>RE Mogul</dc:creator>
		<pubDate>Sun, 09 Nov 2008 05:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/2008/elastic-or-not/#comment-37367</guid>
		<description>Wrap the critical body (main div) information only. Let the toolbars, sidebars, and navigation elements float and expand outside the defined window.

Alternatively, allow navigation elements and sidebars to expand on mouseover -- wrapping it all-in-one.</description>
		<content:encoded><![CDATA[<p>Wrap the critical body (main div) information only. Let the toolbars, sidebars, and navigation elements float and expand outside the defined window.</p>
<p>Alternatively, allow navigation elements and sidebars to expand on mouseover — wrapping it all-in-one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RE Mogul</title>
		<link>http://nickcowie.com/2008/elastic-or-not/comment-page-1/#comment-37039</link>
		<dc:creator>RE Mogul</dc:creator>
		<pubDate>Thu, 26 Jun 2008 18:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/2008/elastic-or-not/#comment-37039</guid>
		<description>&quot;I assume most have reasonable vision.&quot;

My vision is roughly 1/3 of yours -- If I&#039;m zoomed 3x, I see AS WELL as you. I need not be STRICTLY an outlier, though.

Most users compute &quot;hunched.&quot; Most users squint. Visit a busy computer access area for verification, if you must.

A site: ez for me is enjoyable for better eyes, too.

Though (as I&#039;ve probably made clear) I know very little about code/developing I know good web design when I see it! The simplest solution would be: columns. Horizontal scrolling is then PERFECTLY OK, as everyone already has right/left buttons.

Just let the page BE, add modularity so that horizontal is simply an ADDITIONAL navigational feature. Who doesn&#039;t like efficient &amp; ez navigation?

Yes, COLUMNS! Back to Old School.


:::::::::THIS PAGE &gt;&gt; COLUMNS:::::::::

ARTICLE: LEFT
EVERYTHING ELSE: RIGHT

Zooming would essentially transform the 1 page into 2, with horizontal-access to tie them together. 

A zoomed page allows for more comfortable, reclined reading, and who doesn&#039;t want to be comfortable?</description>
		<content:encoded><![CDATA[<p>“I assume most have reasonable vision.”</p>
<p>My vision is roughly 1/3 of yours — If I’m zoomed 3x, I see AS WELL as you. I need not be STRICTLY an outlier, though.</p>
<p>Most users compute “hunched.” Most users squint. Visit a busy computer access area for verification, if you must.</p>
<p>A site: ez for me is enjoyable for better eyes, too.</p>
<p>Though (as I’ve probably made clear) I know very little about code/developing I know good web design when I see it! The simplest solution would be: columns. Horizontal scrolling is then PERFECTLY OK, as everyone already has right/left buttons.</p>
<p>Just let the page BE, add modularity so that horizontal is simply an ADDITIONAL navigational feature. Who doesn’t like efficient &amp; ez navigation?</p>
<p>Yes, COLUMNS! Back to Old School.</p>
<p>:::::::::THIS PAGE » COLUMNS:::::::::</p>
<p>ARTICLE: LEFT<br />
EVERYTHING ELSE: RIGHT</p>
<p>Zooming would essentially transform the 1 page into 2, with horizontal-access to tie them together. </p>
<p>A zoomed page allows for more comfortable, reclined reading, and who doesn’t want to be comfortable?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Buchanan</title>
		<link>http://nickcowie.com/2008/elastic-or-not/comment-page-1/#comment-35487</link>
		<dc:creator>Ben Buchanan</dc:creator>
		<pubDate>Sun, 25 May 2008 14:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/2008/elastic-or-not/#comment-35487</guid>
		<description>Interesting, I had to decide on this for my new blog design. I used a combination of percentage widths and min/max pixel widths. There&#039;s only actually a 250px range, but I catered to 1024x768 as my lowest resolution. 800x600 sees the main content and second column, but has to scroll for the third column.

For your audience though, as described here, I think avoiding horizontal scrolling is a higher priority. So it sounds like your solution is about right.

BTW, there is an IE6 filter for max-width... depends if you&#039;re willing to use filters or not :)</description>
		<content:encoded><![CDATA[<p>Interesting, I had to decide on this for my new blog design. I used a combination of percentage widths and min/max pixel widths. There’s only actually a 250px range, but I catered to 1024x768 as my lowest resolution. 800x600 sees the main content and second column, but has to scroll for the third column.</p>
<p>For your audience though, as described here, I think avoiding horizontal scrolling is a higher priority. So it sounds like your solution is about right.</p>
<p>BTW, there is an IE6 filter for max-width… depends if you’re willing to use filters or not :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://nickcowie.com/2008/elastic-or-not/comment-page-1/#comment-35480</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sun, 25 May 2008 03:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/2008/elastic-or-not/#comment-35480</guid>
		<description>John, yes I had considered max-width, unfortunately a large number of users including all internal users are on ie6 :-(</description>
		<content:encoded><![CDATA[<p>John, yes I had considered max-width, unfortunately a large number of users including all internal users are on ie6 :-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Faulds</title>
		<link>http://nickcowie.com/2008/elastic-or-not/comment-page-1/#comment-35431</link>
		<dc:creator>John Faulds</dc:creator>
		<pubDate>Sat, 24 May 2008 10:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://nickcowie.com/2008/elastic-or-not/#comment-35431</guid>
		<description>Can you not use max-width instead of javascript for constraining the width of the container?</description>
		<content:encoded><![CDATA[<p>Can you not use max-width instead of javascript for constraining the width of the container?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

