<?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>Web Do&#039;s &#38; Don&#039;ts &#187; Javascript</title>
	<atom:link href="http://webdosanddonts.com/tag/javascript/feed" rel="self" type="application/rss+xml" />
	<link>http://webdosanddonts.com</link>
	<description>Tips&#38;Tricks for the modern day web designer</description>
	<lastBuildDate>Mon, 30 Aug 2010 18:18:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Use progressive enhancement instead of graceful degradation</title>
		<link>http://webdosanddonts.com/use-progressive-enhancement-instead-of-graceful-degradation</link>
		<comments>http://webdosanddonts.com/use-progressive-enhancement-instead-of-graceful-degradation#comments</comments>
		<pubDate>Wed, 24 Mar 2010 21:08:49 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[graceful degradation]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[progressive enhancement]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1094</guid>
		<description><![CDATA[It can be said that both progressive enhancement and graceful degradation try to do the same thing: keep our products useful to every user. Progressive enhancement is a more sophisticated and at the same time stable way of assuring that but it takes more time and effort. Graceful degradation can be used more easily as [...]]]></description>
			<content:encoded><![CDATA[<p>It can be said that both progressive enhancement and graceful degradation try to do the same thing: keep our products useful to every user. Progressive enhancement is a more sophisticated and at the same time stable way of assuring that but it takes more time and effort. Graceful degradation can be used more easily as a patch for an already existing product; it means harder maintenance later on, but requires less initial work.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-progressive-enhancement-instead-of-graceful-degradation/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plan the absence of Javascript</title>
		<link>http://webdosanddonts.com/plan-the-absence-of-javascript</link>
		<comments>http://webdosanddonts.com/plan-the-absence-of-javascript#comments</comments>
		<pubDate>Mon, 15 Feb 2010 19:38:05 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=938</guid>
		<description><![CDATA[The fact is that some of your website’s visitors will have JavaScript disabled. Should hidden content remain hidden even if JavaScript is disabled? Should all content be available to screen readers and search engines? If a piece of content becomes visible only after an AJAX call, how do you adequately fill that space when JavaScript [...]]]></description>
			<content:encoded><![CDATA[<p>The fact is that some of your website’s visitors will have JavaScript disabled. Should hidden content remain hidden even if JavaScript is disabled? Should all content be available to screen readers and search engines? If a piece of content becomes visible only after an AJAX call, how do you adequately fill that space when JavaScript is disabled?</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/plan-the-absence-of-javascript/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Avoid issues on handling getElementById</title>
		<link>http://webdosanddonts.com/avoid-issues-on-handling-getelementbyid</link>
		<comments>http://webdosanddonts.com/avoid-issues-on-handling-getelementbyid#comments</comments>
		<pubDate>Sat, 22 Aug 2009 13:28:51 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=503</guid>
		<description><![CDATA[Using the right combination of name and id attributes on a particular element will make getElementById method cross-browser. Yes, even i IE6 and IE7.]]></description>
			<content:encoded><![CDATA[<p>Using the right combination of <code>name</code> and <code>id</code> attributes on a particular element will make <code>getElementById</code> method cross-browser. Yes, even i IE6 and IE7.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/avoid-issues-on-handling-getelementbyid/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
