<?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: Applying Progressive Enhancement to Your CSS</title>
	<atom:link href="http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/</link>
	<description>A resource for Web designers and developers to read about and discuss their craft.</description>
	<lastBuildDate>Wed, 28 Jul 2010 19:29:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Revisiting Progressive Enhancement in CSS - Monday By Noon</title>
		<link>http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1225</link>
		<dc:creator>Revisiting Progressive Enhancement in CSS - Monday By Noon</dc:creator>
		<pubDate>Mon, 17 Mar 2008 13:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1225</guid>
		<description>[...] written about applying progressive enhancement to your CSS in the past, but John&#8217;s article goes above and beyond my idea. To summarize the idea behind [...]</description>
		<content:encoded><![CDATA[<p>[...] written about applying progressive enhancement to your CSS in the past, but John&#8217;s article goes above and beyond my idea. To summarize the idea behind [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1223</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Thu, 22 Mar 2007 13:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1223</guid>
		<description>@David Kees: Personally I have the same as Fredrik in that document.write, to me, isn&#039;t very elegant.  You&#039;re right, it could work.

@Fredrik Wärnsberg:  That&#039;s what I wanted to touch on in the article.  I think something like &lt;code&gt;.hasJS&lt;/code&gt; is another good way to solve the issue at hand.  I&#039;m not a huge fan of separating style sheets to be honest, but I was willing to stretch for this circumstance.</description>
		<content:encoded><![CDATA[<p>@David Kees: Personally I have the same as Fredrik in that document.write, to me, isn&#8217;t very elegant.  You&#8217;re right, it could work.</p>
<p>@Fredrik Wärnsberg:  That&#8217;s what I wanted to touch on in the article.  I think something like <code>.hasJS</code> is another good way to solve the issue at hand.  I&#8217;m not a huge fan of separating style sheets to be honest, but I was willing to stretch for this circumstance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik Wärnsberg</title>
		<link>http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1224</link>
		<dc:creator>Fredrik Wärnsberg</dc:creator>
		<pubDate>Thu, 22 Mar 2007 00:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1224</guid>
		<description>The problem with the method which you mention is that you need to keep your javascript css and your regular css separated.

jQuery&#039;s document.ready() is a nice function, but if you start digging you notice that it relies on browser-sniffing and browser-specific code, which isn&#039;t nice at all.

The document.write() in your head-tag works, but it&#039;s not really that elegant either.

One method that I&#039;ve grown quite fond of is to add the class &quot;hasJS&quot; to the body of the document (not via the document.onLoad-event, but rather in-line javascript just like you suggest in this article). This way you can add js-specific styles to the same css-file using the .hasJS CSS class selector.</description>
		<content:encoded><![CDATA[<p>The problem with the method which you mention is that you need to keep your javascript css and your regular css separated.</p>
<p>jQuery&#8217;s document.ready() is a nice function, but if you start digging you notice that it relies on browser-sniffing and browser-specific code, which isn&#8217;t nice at all.</p>
<p>The document.write() in your head-tag works, but it&#8217;s not really that elegant either.</p>
<p>One method that I&#8217;ve grown quite fond of is to add the class &#8220;hasJS&#8221; to the body of the document (not via the document.onLoad-event, but rather in-line javascript just like you suggest in this article). This way you can add js-specific styles to the same css-file using the .hasJS CSS class selector.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kees</title>
		<link>http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1222</link>
		<dc:creator>David Kees</dc:creator>
		<pubDate>Tue, 20 Mar 2007 15:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1222</guid>
		<description>I&#039;ve use this technique as well, but you don&#039;t have to use DOM creation/manipulation syntax if you don&#039;t want to.  You can just use document.write() to explicitly add the link tag within the head tags of the site.  Either way works, but just about any level of javascript experience can understand document.write() but not everyone&#039;s familiar with the DOM manipulations.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve use this technique as well, but you don&#8217;t have to use DOM creation/manipulation syntax if you don&#8217;t want to.  You can just use document.write() to explicitly add the link tag within the head tags of the site.  Either way works, but just about any level of javascript experience can understand document.write() but not everyone&#8217;s familiar with the DOM manipulations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: All in a days work&#8230;</title>
		<link>http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1221</link>
		<dc:creator>All in a days work&#8230;</dc:creator>
		<pubDate>Tue, 20 Mar 2007 02:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/2007/03/19/applying-progressive-enhancement-to-your-css/#comment-1221</guid>
		<description>[...] Applying Progressive Enhancement to Your CSS (with JavaScript) include the CSS to ‘initialize’ the document in preparation for user interaction via JavaScript. The style will only be applied if your reader has a JavaScript enabled browser (tags: CSS JavaScript) [...]</description>
		<content:encoded><![CDATA[<p>[...] Applying Progressive Enhancement to Your CSS (with JavaScript) include the CSS to ‘initialize’ the document in preparation for user interaction via JavaScript. The style will only be applied if your reader has a JavaScript enabled browser (tags: CSS JavaScript) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using xcache (user agent is rejected)
Database Caching using xcache

Served from: mondaybynoon.com @ 2010-07-30 22:13:01 -->