<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Webmaster-Source &#187; resolution</title>
	<atom:link href="https://www.webmaster-source.com/tag/resolution/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.webmaster-source.com</link>
	<description>Useful Resources For Webmasters</description>
	<lastBuildDate>Thu, 24 Aug 2017 02:01:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>Don&#8217;t Assume a User&#8217;s Browser Window Size</title>
		<link>https://www.webmaster-source.com/2011/06/29/dont-assume-a-users-browser-window-size/</link>
		<comments>https://www.webmaster-source.com/2011/06/29/dont-assume-a-users-browser-window-size/#comments</comments>
		<pubDate>Wed, 29 Jun 2011 11:35:21 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[resolution]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=4136</guid>
		<description><![CDATA[Chris Coyier has an amazing article that finally puts the screen resolution myth to rest. Despite screen resolutions getting progressively bigger, the available width for your web designs is not. If you have a ginormous 30-inch monitor, you probably don&#8217;t keep your web browser full-screen. You probably have it at a more comfortable size and [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Chris Coyier has <a href="http://css-tricks.com/9778-screen-resolution-notequalto-browser-window/">an amazing article</a> that finally puts the screen resolution myth to rest. Despite screen resolutions getting progressively bigger, the available width for your web designs is not. If you have a ginormous 30-inch monitor, you probably don&#8217;t keep your web browser full-screen. You probably have it at a more comfortable size and use the extra space to keep other things visible simultaneously. (This goes double for Mac users, who don&#8217;t really have the whole &#8220;full screen&#8221; habit to begin with.)</p>
<p>The post also demonstrates a way to use a bit of jQuery magic to record users&#8217; browser window sizes and dump it into a database, since Google Analytics does not yet provide this metric.</p>
<p>Practically, it&#8217;s still best to use the old &#8220;keep it under a thousand pixels&#8221; rule. It matches up well with the most common browser window ranges, and many of us have lower screen resolutions anyway. I primarily use a 13&#8243; laptop with a 1200-pixel wide LCD. That means I keep Firefox resized to be around one thousand pixels wide, leaving some breathing room while still being able to view most web sites without annoying horizontal scroll bars.</p>
<p><a href="http://css-tricks.com/9778-screen-resolution-notequalto-browser-window/">Screen Resolution ≠ Browser Window</a> [CSS-Tricks]</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2011/06/29/dont-assume-a-users-browser-window-size/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iPhone 4 Gets a 326ppi Screen: What Does this Mean for Web Design?</title>
		<link>https://www.webmaster-source.com/2010/06/25/iphone-4-gets-a-326ppi-screen-what-does-this-mean-for-web-design/</link>
		<comments>https://www.webmaster-source.com/2010/06/25/iphone-4-gets-a-326ppi-screen-what-does-this-mean-for-web-design/#comments</comments>
		<pubDate>Fri, 25 Jun 2010 11:24:53 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[resolution]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=3417</guid>
		<description><![CDATA[The new iPhone 4&#8217;s screen may be the same size as its predecessor&#8217;s, but the resolution is much higher. 326 pixels per inch, versus the 160ppi of the previous models. (This works out to pixel dimensions of 960&#215;640 for the new model and 320&#215;480 for the old, but that&#8217;s not really relevant to this post.) [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The <a href="http://www.mobilecrunch.com/2010/06/07/side-by-side-just-how-much-better-does-the-iphone-4s-display-look/">new iPhone 4&#8217;s screen</a> may be the same size as its predecessor&#8217;s, but the resolution is much higher. 326 pixels per inch, versus the 160ppi of the previous models. (This works out to pixel dimensions of 960&#215;640 for the new model and 320&#215;480 for the old, but that&#8217;s not really relevant to this post.) 326ppi is roughly the same resolution as is used in printing images, as opposed to the 72-96 pixels per inch that most web designers design for.</p>
<p>Already, if you view an iPhone screenshot on a computer monitor, it will look strangely oversized due to the difference in resolution. The new &#8220;retina display&#8221; will make the effect further pronounced.</p>
<p style="text-align: center;"><a href="http://www.mobilecrunch.com/2010/06/07/side-by-side-just-how-much-better-does-the-iphone-4s-display-look/"><img style=' display: block; margin-right: auto; margin-left: auto;'  class="size-full wp-image-3418 aligncenter imgborder" title="iPhone 4 &quot;retina display.&quot; Image credit: MobileCrunch.com" src="//www.webmaster-source.com/wp-content/uploads/iphone4-retina-display.jpg" alt="" width="600" height="262" /></a></p>
<p>My question is: with phone displays increasing in resolution, can we assume that desktop and laptop monitors will follow? Will it become more common to see full-size screens with upwards of 300ppi? It might cause some problems for designers at first, but it will make for more richly detailed web designs eventually.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2010/06/25/iphone-4-gets-a-326ppi-screen-what-does-this-mean-for-web-design/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>FoldSpy: Find The Fold</title>
		<link>https://www.webmaster-source.com/2008/05/30/foldspy-find-the-fold/</link>
		<comments>https://www.webmaster-source.com/2008/05/30/foldspy-find-the-fold/#comments</comments>
		<pubDate>Fri, 30 May 2008 11:14:09 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[fold]]></category>
		<category><![CDATA[resolution]]></category>
		<category><![CDATA[screen]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=570</guid>
		<description><![CDATA[&#8220;Above the fold&#8221; refers to the section of a webpage immediately visible without scrolling. It&#8217;s a carryover from the days of newspapers, where the biggest story would go on the front page, above the fold in the paper. Back when newspapers ruled the earth (yes, I&#8217;m unconsciously trying to make print media sound prehistoric), The [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>&#8220;Above the fold&#8221; refers to the section of a webpage immediately visible without scrolling. It&#8217;s a carryover from the days of newspapers, where the biggest story would go on the front page, above the fold in the paper.</p>
<p>Back when newspapers ruled the earth (yes, I&#8217;m unconsciously trying to make print media sound prehistoric), The Fold was a physical crease in the paper. Nowadays it&#8217;s a bit more complicated. You have different screen sizes and resolutions, toolbars that take-up room in the browser, and some people resize their browser window differently&#8230; There are a lot of factors.<span id="more-570"></span></p>
<p><a href="http://www.foldspy.com/">FoldSpy</a> is an interesting little bit of JavaScript magic that let&#8217;s you see where the fold is on people&#8217;s computers. Once you place the script on your site, you activate it by visiting <code>http://yourdomain.com/#foldspy</code>. An interactive overlay appears, allowing you too see what parts of your site are visible above the fold by different people. As you adjust the overlay, you&#8217;re shown a percentage based calculated by the viewport size data collected from all of the sites that use FoldSpy.</p>
<p><img src="http://i30.tinypic.com/22bxar.jpg" alt="" width="500" height="242" /></p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2008/05/30/foldspy-find-the-fold/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixed vs. Liquid Layouts</title>
		<link>https://www.webmaster-source.com/2008/05/21/fixed-vs-liquid-layouts/</link>
		<comments>https://www.webmaster-source.com/2008/05/21/fixed-vs-liquid-layouts/#comments</comments>
		<pubDate>Wed, 21 May 2008 11:20:55 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[fixed]]></category>
		<category><![CDATA[Internet Explorer]]></category>
		<category><![CDATA[layout]]></category>
		<category><![CDATA[liquid]]></category>
		<category><![CDATA[monitor]]></category>
		<category><![CDATA[resolution]]></category>
		<category><![CDATA[screen]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=558</guid>
		<description><![CDATA[This is yet another web-related topic that gets people arguing. Not quite as bad as &#8220;Mac vs. PC,&#8221; it really gets some people going. Which is better, a fixed-width layout, or a fluid one that resizes to fit the browser window. Unlike some people, I say that it depends on the project, and that there [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><img class="alignright" style="float: right; margin: 5px;;  float: right; padding: 4px; margin: 0 0 2px 7px;" src="http://i31.tinypic.com/15cljsk.gif" alt="" width="250" height="120" />This is yet another web-related topic that gets people arguing. Not quite as bad as &#8220;Mac vs. PC,&#8221; it really gets some people going. Which is better, a fixed-width layout, or a fluid one that resizes to fit the browser window. Unlike <em>some</em> people, I say that it depends on the project, and that there isn&#8217;t a one-size-fits-all solution (though I do lean <em>slightly</em> toward fixed-width layouts). Besides, if we all agreed on standards for everything, we wouldn&#8217;t have anything to argue about..</p>
<p>Both sides of the argument have their pluses and minuses, and generally I would say &#8220;go with what best suits the instance.&#8221; If you want a certain look, which will require vertical tile images, and other images of specific width, you may need to go with a fixed-width layout. If you want as much control as you can get over the look of your design, or if you need your content area to be a specific size, go with a fixed layout.<span id="more-558"></span></p>
<p>Liquid layouts can adapt to the available space in the browser&#8217;s viewport, which makes a site more accessible, avoiding the annoying horizontal scrollbar that fixed-width layouts often generate at low resolutions. If you can put together a good-looking liquid layout that works well in your given scenario, go for it. However, you must rely on the CSS attributes min-width and max-width to make sure that your design can&#8217;t shrink too much, squishing your beautiful design into an illegible mess, or two wide, making for long, hard-to-read lines of text on large widescreen monitors. Too bad the attributes don&#8217;t work on Internet Explorer 6 (big surprise)!</p>
<p>You could also go for a hybrid layout where parts of the design are fixed, and others liquid. You could have a fixed-width sidebar with a liquid content column, for example. I&#8217;ve found that this method works better than having everything based off percentages of ems.</p>
<p>Unfortunately, we&#8217;re plagued by small groups of people with low-resolution monitors, very big widescreen monitors, tiny mobile web phones, and outdated browsers like Internet Explorer. We&#8217;re ill-equipped to handle all the possible scenarios, and far too many people don&#8217;t update their browsers in a timely manner, resulting in a lack of improvement in that area. All we can really do is support as many browsers and resolutions as possible, and wait for people&#8217;s computers to stop working, so they will get a modern machine, resulting in a tiny step forward progress-wise. Eventually Internet Explorer 6 will die-out, giving us better support for liquid layouts, which are becoming more and more important as screen resolutions diversify, having increasingly different aspect ratios as well as pixel dimensions.</p>
<h3>Further Reading&#8230;</h3>
<p>I managed to dig-up a post I found via Smashing Magazine back in August 2007. &#8211; <a href="http://green-beast.com/blog/?p=199">CSS Layouts: The Fixed. The Fluid. The Elastic.</a></p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2008/05/21/fixed-vs-liquid-layouts/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/


Served from: www.webmaster-source.com @ 2026-06-09 04:07:55 by W3 Total Cache
-->