<?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: IE6, IE7, IE8, web standards IE6, IE7, IE8, web standards</title>
	<atom:link href="http://ghettocooler.net/2008/03/17/ie6-ie7-ie8/feed/" rel="self" type="application/rss+xml" />
	<link>http://ghettocooler.net/2008/03/17/ie6-ie7-ie8/</link>
	<description></description>
	<lastBuildDate>Thu, 10 Nov 2011 19:44:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Bill</title>
		<link>http://ghettocooler.net/2008/03/17/ie6-ie7-ie8/comment-page-1/#comment-50021</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Tue, 18 Mar 2008 13:25:37 +0000</pubDate>
		<guid isPermaLink="false">http://ghettocooler.net/2008/03/17/ie6-ie7-ie8/#comment-50021</guid>
		<description>Thanks Foxxyz

This is what I suspected, and yet all the coverage seems to blame all the IE8 issues on web standards. The web is way deeper than it&#039;s presentation!</description>
		<content:encoded><![CDATA[<p>Thanks Foxxyz</p>
<p>This is what I suspected, and yet all the coverage seems to blame all the IE8 issues on web standards. The web is way deeper than it&#8217;s presentation!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: foxxyz</title>
		<link>http://ghettocooler.net/2008/03/17/ie6-ie7-ie8/comment-page-1/#comment-49985</link>
		<dc:creator>foxxyz</dc:creator>
		<pubDate>Tue, 18 Mar 2008 05:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://ghettocooler.net/2008/03/17/ie6-ie7-ie8/#comment-49985</guid>
		<description>Cross-browser Javascript really is much more of a mess than CSS is. I find that nearly 95% of my CSS works perfectly fine on IE7 and am pretty happy with the results overall. Mind you, that is with well-written CSS and proper semantic HTML. Like you said, it&#039;s just IE6 that needs a bit of an extra push (or two), but it&#039;s fine to handle that with the &lt;code&gt;&#039;* html&#039;&lt;/code&gt; hack, which all other browsers ignore - as they should.

I think it&#039;s a bit different with Javascript. It is those tiny changes to the DOM handling that are disastrous to AJAX apps like GMail and GMaps. Especially because all Google&#039;s JS was written by themselves and deals with all the tiny inconsistencies between browsers that obviously break when IE8 comes along.

There&#039;s nothing to worry about for all of us spoiled with jQuery or Prototype. When IE8 comes out, so will a new version of those libraries and suddenly the internet will appear not to have changed too much at all. 

Mmmm, internet, how do you always stay so comfy and fluffy?</description>
		<content:encoded><![CDATA[<p>Cross-browser Javascript really is much more of a mess than CSS is. I find that nearly 95% of my CSS works perfectly fine on IE7 and am pretty happy with the results overall. Mind you, that is with well-written CSS and proper semantic HTML. Like you said, it&#8217;s just IE6 that needs a bit of an extra push (or two), but it&#8217;s fine to handle that with the <code>'* html'</code> hack, which all other browsers ignore &#8211; as they should.</p>
<p>I think it&#8217;s a bit different with Javascript. It is those tiny changes to the DOM handling that are disastrous to AJAX apps like GMail and GMaps. Especially because all Google&#8217;s JS was written by themselves and deals with all the tiny inconsistencies between browsers that obviously break when IE8 comes along.</p>
<p>There&#8217;s nothing to worry about for all of us spoiled with jQuery or Prototype. When IE8 comes out, so will a new version of those libraries and suddenly the internet will appear not to have changed too much at all. </p>
<p>Mmmm, internet, how do you always stay so comfy and fluffy?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

