<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Scroll Stoppers at MensHealth.com</title>
	<atom:link href="http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 11 Feb 2012 08:11:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Phil</title>
		<link>http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/comment-page-1/#comment-72700</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Thu, 19 Apr 2007 20:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/#comment-72700</guid>
		<description>Good point.  We are working through a redesign to our home page at rezoom.com and have had to take this into consideration.  We are adding a number of modular widgets to display different data and we are currently working on testing different browser sizes for &quot;first impression&quot; looks just to be sure all our fancy new modules get some attention if they are below the page line.

If anyone reading doesn&#039;t already know about it, browsercam.com is a good resource for seeing your site on a number of different browser and resolution combinations.  They basically just load it up and creat screen captures and send them to you.  Pretty niffty.</description>
		<content:encoded><![CDATA[<p>Good point.  We are working through a redesign to our home page at rezoom.com and have had to take this into consideration.  We are adding a number of modular widgets to display different data and we are currently working on testing different browser sizes for &#8220;first impression&#8221; looks just to be sure all our fancy new modules get some attention if they are below the page line.</p>
<p>If anyone reading doesn&#8217;t already know about it, browsercam.com is a good resource for seeing your site on a number of different browser and resolution combinations.  They basically just load it up and creat screen captures and send them to you.  Pretty niffty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kendall</title>
		<link>http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/comment-page-1/#comment-71244</link>
		<dc:creator>Kendall</dc:creator>
		<pubDate>Sat, 14 Apr 2007 14:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/#comment-71244</guid>
		<description>Well if you check out the source code for Men&#039;s Health you&#039;ll see why it has issues. It has some of the ugliest code I ever did see. They really need to work on their layouts though. The problem you identify is definitely a problem.</description>
		<content:encoded><![CDATA[<p>Well if you check out the source code for Men&#8217;s Health you&#8217;ll see why it has issues. It has some of the ugliest code I ever did see. They really need to work on their layouts though. The problem you identify is definitely a problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Bunzol</title>
		<link>http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/comment-page-1/#comment-70961</link>
		<dc:creator>Jim Bunzol</dc:creator>
		<pubDate>Fri, 13 Apr 2007 13:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/#comment-70961</guid>
		<description>Here&#039;s a bit of irony for you.  I emailed a link to this article to my colleagues and we encountered a literal &quot;scroll stopper&quot; on this page.  When my colleague clicked the link, the bottom of the page was where the &quot;Podcast Powered by&quot; text is located on the right side of the page.  He was unable to scroll any further.

My first question was what operating system (Windows XP, same as me) and my next question was screen resolution (1024x768, mine was 1280x1024).  Both browsers were IE 6.  

Since I was unable to recreate this issue at 1280x1024, I then switched to 1024x768 resolution and, snap, there it was.  This page literally stopped where the &quot;Podcast Powered by&quot; text is located on the right side of the page.  I had to refresh the page to be able to view the rest of the screen.  I tested this with multiple users and came to the same conclusion.  

Now after switching back to 1280x1024, the same issue is recurring everytime I click the link to the page.  I then tested the scenario with a fourth user and found that if the user has no browser window open and clicks the link, the page will not fully display, however, if there is already a browser window open and the user clicks the link, then the page will fully display in the already open browser window.  I then realized that it has nothing to do with the screen resolution, but rather if the page opens in a new window or in an existing window.

I only find this comment important because if people don&#039;t realize there is more to this page, they will miss the link to the article &quot;As the Page Scrolls&quot; which is at the end of this article.  Of course if this does happen, the user will also not see the comments section which renders this particular comment moot. Both articles are excellent reading.  :)</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a bit of irony for you.  I emailed a link to this article to my colleagues and we encountered a literal &#8220;scroll stopper&#8221; on this page.  When my colleague clicked the link, the bottom of the page was where the &#8220;Podcast Powered by&#8221; text is located on the right side of the page.  He was unable to scroll any further.</p>
<p>My first question was what operating system (Windows XP, same as me) and my next question was screen resolution (1024&#215;768, mine was 1280&#215;1024).  Both browsers were IE 6.  </p>
<p>Since I was unable to recreate this issue at 1280&#215;1024, I then switched to 1024&#215;768 resolution and, snap, there it was.  This page literally stopped where the &#8220;Podcast Powered by&#8221; text is located on the right side of the page.  I had to refresh the page to be able to view the rest of the screen.  I tested this with multiple users and came to the same conclusion.  </p>
<p>Now after switching back to 1280&#215;1024, the same issue is recurring everytime I click the link to the page.  I then tested the scenario with a fourth user and found that if the user has no browser window open and clicks the link, the page will not fully display, however, if there is already a browser window open and the user clicks the link, then the page will fully display in the already open browser window.  I then realized that it has nothing to do with the screen resolution, but rather if the page opens in a new window or in an existing window.</p>
<p>I only find this comment important because if people don&#8217;t realize there is more to this page, they will miss the link to the article &#8220;As the Page Scrolls&#8221; which is at the end of this article.  Of course if this does happen, the user will also not see the comments section which renders this particular comment moot. Both articles are excellent reading.  <img src='http://www.uie.com/brainsparks/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Portigal</title>
		<link>http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/comment-page-1/#comment-70795</link>
		<dc:creator>Steve Portigal</dc:creator>
		<pubDate>Thu, 12 Apr 2007 23:18:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/04/12/scroll-stoppers-at-menshealthcom/#comment-70795</guid>
		<description>I encountered one of these today! I signed up for a shipping account at FedEx.com and it walks through filling out various bits of content, contact info, then credit info, etc. All the zones are available on screen, but the credit card info (except for the title) is below the fold. The contact info was already populated, so I tweaked one or two fields and hit the associated continue button. The status bar told me it was loading a page about credit card, but it was exactly the same page, as if there was some error in the address or something. I tried this several times and somehow I ended up scrolling down to see that the credit section was also waiting to be filled in, with its OWN continue button. I don&#039;t know what made me scroll, but it&#039;s clear that the visual cues were absolutely scroll stoppers. In this case, scroll stopping 100% broke the registration process. Bad fedex.com, bad.</description>
		<content:encoded><![CDATA[<p>I encountered one of these today! I signed up for a shipping account at FedEx.com and it walks through filling out various bits of content, contact info, then credit info, etc. All the zones are available on screen, but the credit card info (except for the title) is below the fold. The contact info was already populated, so I tweaked one or two fields and hit the associated continue button. The status bar told me it was loading a page about credit card, but it was exactly the same page, as if there was some error in the address or something. I tried this several times and somehow I ended up scrolling down to see that the credit section was also waiting to be filled in, with its OWN continue button. I don&#8217;t know what made me scroll, but it&#8217;s clear that the visual cues were absolutely scroll stoppers. In this case, scroll stopping 100% broke the registration process. Bad fedex.com, bad.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

