<?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: Battling with IE &#8211; 4 CSS methods</title>
	<atom:link href="http://tnels.com/2008/03/27/battling-with-ie-4-css-methods/feed/" rel="self" type="application/rss+xml" />
	<link>http://tnels.com/2008/03/27/battling-with-ie-4-css-methods/</link>
	<description>Now with posts!</description>
	<lastBuildDate>Tue, 26 Jul 2011 16:20:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: t.nels</title>
		<link>http://tnels.com/2008/03/27/battling-with-ie-4-css-methods/comment-page-1/#comment-39</link>
		<dc:creator>t.nels</dc:creator>
		<pubDate>Fri, 28 Mar 2008 02:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://tnels.com/2008/03/27/battling-with-ie-4-css-methods.html#comment-39</guid>
		<description>Excellent points Jason. I read an article somewhere about a movement to put &quot;Get a real browser&quot; button linking to Firefox, but I can&#039;t support making it hard for IE users to actually use the internet. Then we become just as bad as them. IE is digging their own grave... See my upcoming rant on Safari 3.1 (part 3).

Also, there&#039;s a couple places for people like you and me to promote well built browsers to those who might need them. Check out http://www.spreadfirefox.com/ and http://browsehappy.com/. Both great sites.

And thanks for the tip on Blueprint. I&#039;ll have to check that out.</description>
		<content:encoded><![CDATA[<p>Excellent points Jason. I read an article somewhere about a movement to put &#8220;Get a real browser&#8221; button linking to Firefox, but I can&#8217;t support making it hard for IE users to actually use the internet. Then we become just as bad as them. IE is digging their own grave&#8230; See my upcoming rant on Safari 3.1 (part 3).</p>
<p>Also, there&#8217;s a couple places for people like you and me to promote well built browsers to those who might need them. Check out <a href="http://www.spreadfirefox.com/" rel="nofollow">http://www.spreadfirefox.com/</a> and <a href="http://browsehappy.com/" rel="nofollow">http://browsehappy.com/</a>. Both great sites.</p>
<p>And thanks for the tip on Blueprint. I&#8217;ll have to check that out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Martinez</title>
		<link>http://tnels.com/2008/03/27/battling-with-ie-4-css-methods/comment-page-1/#comment-38</link>
		<dc:creator>Jason Martinez</dc:creator>
		<pubDate>Fri, 28 Mar 2008 01:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://tnels.com/2008/03/27/battling-with-ie-4-css-methods.html#comment-38</guid>
		<description>This is definitely an article I wished I had all together while working through the kwirks of IE. I&#039;ve found that blueprint css framework also gives you a great base of styles and markup to work with that help stay away from IE problems. Blueprint is a great resource and you can pick and choose what pieces of it to use to some extent, great stuff.

Otherwise I&#039;ve been thinking about some standard widget on pages that will let the web community get rid of IE a little quicker than Microsoft would hope. I know they are preparing IE8 to be really standards compliant, but as always, who wants to wait for them? We have standards compliant browsers, Safari 3 nightlies now pass the acid 3 test 100/100 so IE should really just be unsupported and it&#039;s us web developers who can start that... So here&#039;s the idea...

A tiny little JS include that anybody can throw in their page that shows little boxes somewhere for browsers. You would &quot;light up&quot; the browsers you support and leave IE greyed out if your site doesn&#039;t support it. The JS would also include a lightbox that pops up letting old IE users or IE users in general know that their browser is &quot;not supported&quot; and that they need to upgrade or preferrably, use a real browser (with links for them to get em). I have a feeling the web community is going to force this before microsoft ever gives up. It&#039;s a method some hate but I like the idea of the folks on the internet telling MS that we won&#039;t wait for their crappy products any longer.</description>
		<content:encoded><![CDATA[<p>This is definitely an article I wished I had all together while working through the kwirks of IE. I&#8217;ve found that blueprint css framework also gives you a great base of styles and markup to work with that help stay away from IE problems. Blueprint is a great resource and you can pick and choose what pieces of it to use to some extent, great stuff.</p>
<p>Otherwise I&#8217;ve been thinking about some standard widget on pages that will let the web community get rid of IE a little quicker than Microsoft would hope. I know they are preparing IE8 to be really standards compliant, but as always, who wants to wait for them? We have standards compliant browsers, Safari 3 nightlies now pass the acid 3 test 100/100 so IE should really just be unsupported and it&#8217;s us web developers who can start that&#8230; So here&#8217;s the idea&#8230;</p>
<p>A tiny little JS include that anybody can throw in their page that shows little boxes somewhere for browsers. You would &#8220;light up&#8221; the browsers you support and leave IE greyed out if your site doesn&#8217;t support it. The JS would also include a lightbox that pops up letting old IE users or IE users in general know that their browser is &#8220;not supported&#8221; and that they need to upgrade or preferrably, use a real browser (with links for them to get em). I have a feeling the web community is going to force this before microsoft ever gives up. It&#8217;s a method some hate but I like the idea of the folks on the internet telling MS that we won&#8217;t wait for their crappy products any longer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

