<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Forum | studiograsshopper</title>
	<link>http://www.studiograsshopper.ch/forum/general-discussion/more-misleading-browser-errors/</link>
	<description><![CDATA[Wordpress development, plugins, code ideas and babycakes*]]></description>
	<generator>Simple:Press Version 4.3.2</generator>
	<atom:link href="http://www.studiograsshopper.ch/forum/?general-discussion&#038;more-misleading-browser-errors&#038;xfeed=topic" rel="self" type="application/rss+xml" />
<item>
	<title>Ade on More misleading browser errors</title>
	<link>http://www.studiograsshopper.ch/forum/general-discussion/more-misleading-browser-errors/#p48</link>
	<category>General Discussion</category>
	<guid isPermaLink="true">http://www.studiograsshopper.ch/forum/general-discussion/more-misleading-browser-errors/#p48</guid>
	<description><![CDATA[<p>Why do certain browsers insist on "correcting" coding errors? Over the last few months I have come across a few situations where Firefox - the darling of the web development world - "corrects" a coding error which, in my opinion, should not be corrected.</p>
<p>What's the problem with that, I hear you ask? Well, in my view, this can be a dangerous situation if one tends to rely on Firefox as being the "perfect" browser for developing web sites. Personally, if I've made a coding error I want to know about it so that I can correct it and ensure, all ...</p>
]]></description>
	<pubDate>Sat, 08 Nov 2008 22:17:53 +0000</pubDate>
</item>
</channel>
</rss>