<?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: Evolution of the Widget</title>
	<atom:link href="http://www.beaconfire.com/blog/2010/08/evolution-of-the-widget/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.beaconfire.com/blog/2010/08/evolution-of-the-widget/</link>
	<description></description>
	<lastBuildDate>Wed, 08 May 2013 17:11:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Tim</title>
		<link>http://www.beaconfire.com/blog/2010/08/evolution-of-the-widget/comment-page-1/#comment-33678</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 04 Aug 2010 15:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.beaconfire.com/blog/?p=2073#comment-33678</guid>
		<description><![CDATA[You mention that the size is sometimes a factor and I thought I&#039;d throw in another example of why this is true.  When we test across different browsers there are almost always slight variances in the ways IE, Firefox, and Safari render fonts and sizes of things (even between Mac and PC).  For the most part, an item being a few pixels lower on the page in Safari than it is in Firefox is not a problem.  But when you are building a widget that is only 200 pixels tall to begin with, those small discrepancies can quickly become the difference between &quot;working&quot; and &quot;not working.&quot;  I&#039;m always surprised by how much more back and forth there tends to be when testing the layouts of widgets as opposed to full sites.]]></description>
		<content:encoded><![CDATA[<p>You mention that the size is sometimes a factor and I thought I&#8217;d throw in another example of why this is true.  When we test across different browsers there are almost always slight variances in the ways IE, Firefox, and Safari render fonts and sizes of things (even between Mac and PC).  For the most part, an item being a few pixels lower on the page in Safari than it is in Firefox is not a problem.  But when you are building a widget that is only 200 pixels tall to begin with, those small discrepancies can quickly become the difference between &#8220;working&#8221; and &#8220;not working.&#8221;  I&#8217;m always surprised by how much more back and forth there tends to be when testing the layouts of widgets as opposed to full sites.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
