<?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: CSS Browser Selector</title>
	<atom:link href="http://www.45royale.com/blog/articles/css-browser-selector/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.45royale.com/blog/articles/css-browser-selector/</link>
	<description>A web design studio in Atlanta, Georgia.</description>
	<lastBuildDate>Mon, 26 Jul 2010 21:27:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam Little</title>
		<link>http://www.45royale.com/blog/articles/css-browser-selector/comment-page-1/#comment-9117</link>
		<dc:creator>Adam Little</dc:creator>
		<pubDate>Fri, 10 Jul 2009 20:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.45royale.com/?p=1632#comment-9117</guid>
		<description>&lt;strong&gt;Jon&lt;/strong&gt;, thanks for the comment!  You bring up a good point, and it&#039;s one we definitely considered before we started our last redesign effort.  The good news is, if a user has javascript disabled, a site should still be usable, they just won&#039;t have as good of an experience as someone who has it enabled.

It&#039;s hard to find actual data on how many users have javascript disabled, but according to browser statistics like &lt;a href=http://www.w3schools.com/browsers/browsers_stats.asp&quot; title=&quot;Browser Statistics&quot; rel=&quot;nofollow&quot;&gt;this one&lt;/a&gt; from &lt;a href=&quot;http://www.w3schools.com/&quot; title=&quot;w3schools.com&quot; rel=&quot;nofollow&quot;&gt;w3schools.com&lt;/a&gt;, only about 5% of internet users have javascript disabled.  It&#039;s hard to validate these numbers since lot of software tracking packages, like Google Analytics, rely on javascript to capture data.  As a result, &lt;strong&gt;visitors with javascript disabled are absent from many statistic reports.&lt;/strong&gt;

For sites that we build and maintain, including 45royale.com, we want to have pages render well across as many browsers as possible without weakening the design.  There are a lot of browser hacks available that we&#039;ve used in the past to achieve this effect, but they aren&#039;t nearly as robust and clean as this script.  For us, we&#039;d rather use a script like this to offer a great experience to 95% of internet users regardless of their browser vs. having to pair back on the design of a new site in order to appeal to that remaining 5% of users.</description>
		<content:encoded><![CDATA[<p><strong>Jon</strong>, thanks for the comment!  You bring up a good point, and it&#8217;s one we definitely considered before we started our last redesign effort.  The good news is, if a user has javascript disabled, a site should still be usable, they just won&#8217;t have as good of an experience as someone who has it enabled.</p>
<p>It&#8217;s hard to find actual data on how many users have javascript disabled, but according to browser statistics like <a href=http://www.w3schools.com/browsers/browsers_stats.asp" title="Browser Statistics" rel="nofollow">this one</a> from <a href="http://www.w3schools.com/" title="w3schools.com" rel="nofollow">w3schools.com</a>, only about 5% of internet users have javascript disabled.  It&#8217;s hard to validate these numbers since lot of software tracking packages, like Google Analytics, rely on javascript to capture data.  As a result, <strong>visitors with javascript disabled are absent from many statistic reports.</strong></p>
<p>For sites that we build and maintain, including 45royale.com, we want to have pages render well across as many browsers as possible without weakening the design.  There are a lot of browser hacks available that we&#8217;ve used in the past to achieve this effect, but they aren&#8217;t nearly as robust and clean as this script.  For us, we&#8217;d rather use a script like this to offer a great experience to 95% of internet users regardless of their browser vs. having to pair back on the design of a new site in order to appeal to that remaining 5% of users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.45royale.com/blog/articles/css-browser-selector/comment-page-1/#comment-8823</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 08 Jul 2009 06:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.45royale.com/?p=1632#comment-8823</guid>
		<description>Sounds great, but what if the user has javascript disabled?</description>
		<content:encoded><![CDATA[<p>Sounds great, but what if the user has javascript disabled?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Little</title>
		<link>http://www.45royale.com/blog/articles/css-browser-selector/comment-page-1/#comment-873</link>
		<dc:creator>Adam Little</dc:creator>
		<pubDate>Sat, 21 Feb 2009 14:38:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.45royale.com/?p=1632#comment-873</guid>
		<description>Awesome, glad you guys like the post!  Browser testing can be frustrating at times, but this method at least gives me a clean way to target any browser I want.  @Daniel, I&#039;ll second what you said, it is definitely one of the best tools I have in my browser testing arsenal.</description>
		<content:encoded><![CDATA[<p>Awesome, glad you guys like the post!  Browser testing can be frustrating at times, but this method at least gives me a clean way to target any browser I want.  @Daniel, I&#8217;ll second what you said, it is definitely one of the best tools I have in my browser testing arsenal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Veiga</title>
		<link>http://www.45royale.com/blog/articles/css-browser-selector/comment-page-1/#comment-863</link>
		<dc:creator>Daniel Veiga</dc:creator>
		<pubDate>Fri, 20 Feb 2009 17:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.45royale.com/?p=1632#comment-863</guid>
		<description>I&#039;ve been using this on my projects that I create for over 6 months now and it&#039;s wonderful, one of the best tools that I have for development and testing.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using this on my projects that I create for over 6 months now and it&#8217;s wonderful, one of the best tools that I have for development and testing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Brown</title>
		<link>http://www.45royale.com/blog/articles/css-browser-selector/comment-page-1/#comment-708</link>
		<dc:creator>Kevin Brown</dc:creator>
		<pubDate>Fri, 13 Feb 2009 04:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.45royale.com/?p=1632#comment-708</guid>
		<description>This is a great resource!  I&#039;ll most certainly use this on future projects!  Thanks a lot!</description>
		<content:encoded><![CDATA[<p>This is a great resource!  I&#8217;ll most certainly use this on future projects!  Thanks a lot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cssProdigy</title>
		<link>http://www.45royale.com/blog/articles/css-browser-selector/comment-page-1/#comment-705</link>
		<dc:creator>cssProdigy</dc:creator>
		<pubDate>Thu, 12 Feb 2009 23:00:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.45royale.com/?p=1632#comment-705</guid>
		<description>Great post! I&#039;m looking forward to the day when all browsers will be standards-compliant, until then we&#039;ll have to deal with what we&#039;ve got.</description>
		<content:encoded><![CDATA[<p>Great post! I&#8217;m looking forward to the day when all browsers will be standards-compliant, until then we&#8217;ll have to deal with what we&#8217;ve got.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
