<?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>WallOfScribbles &#187; Standards</title>
	<atom:link href="http://wallofscribbles.com/tag/standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://wallofscribbles.com</link>
	<description>The ramblings of a man</description>
	<lastBuildDate>Sat, 07 Jan 2012 01:14:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Apparently IE8 is Causing Ruckus</title>
		<link>http://wallofscribbles.com/2008/apparently-ie8-is-causing-ruckus/</link>
		<comments>http://wallofscribbles.com/2008/apparently-ie8-is-causing-ruckus/#comments</comments>
		<pubDate>Fri, 25 Jan 2008 05:05:53 +0000</pubDate>
		<dc:creator>Corey Dutson</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Internet Explorer]]></category>
		<category><![CDATA[Standards]]></category>

		<guid isPermaLink="false">http://www.wallofscribbles.com/2008/01/25/apparently-ie8-is-causing-ruckus/</guid>
		<description><![CDATA[You heard me people: <em>ruckus</em>.

For those not in the know, I'm talking about the apparent <a href="http://blogs.msdn.com/ie/archive/2008/01/21/compatibility-and-ie8.aspx" title="browser version targeting" target="_blank">browser version targeting</a> that the IE8 team is going to be providing. This has caused a bit of a split amongst the web community. I won't go into excessive detail over the topic, because there are <a href="http://alistapart.com/articles/beyonddoctype" title="A List Apart" target="_blank">others</a> that have <a href="http://alistapart.com/articles/fromswitchestotargets" title="A List Apart" target="_blank">expanded</a> upon it as <a href="http://www.timkadlec.com/post.asp?q=41" title="Tim Kadlec" target="_blank">much</a> as humanly possible.]]></description>
			<content:encoded><![CDATA[<p>The gist is this: You can tell the browser how to render your web page.  I&#8217;m aware that that&#8217;s how it should be working from the get go, but as we learned with the IE7 chaos that this is not the case. Microsoft&#8217;s solution is a simple meta-tag that you would add to your markup which would allow your website to tell the browser (IE8) to act like IE7 or IE6 or whatever version your site looked pretty in. This is great if you&#8217;re a lazy markup-writer, or cannot honestly be bothered with updating your website in any shape, way, or form. I can see the merit, truly I can. It&#8217;s a total cop-out with the whole &#8220;continuous improvement&#8221; idea that mankind is always raving about, but who really needs that? A part of me is a real fan of this idea based solely on past experiences with styling in IE.</p>
<p>Now granted, you can tell your website to stay on the cutting edge of IE rendering by using the &#8220;edge&#8221; keyword (see what I did there?) in your meta-tag . This will allow your website to be rendered at whatever the end users version of IE is. I like the idea of targeting a website to certain browsers, especially when you work in a web development position where part of the statement of work is a section dedicated to what browsers your work has to run in. This sort of idea makes my job as a website stylist that much easier. Unfortunately, I am opposed to the idea in the end.</p>
<p>The problem lays not in the fact that you can target browser version, it&#8217;s the fact that it&#8217;s gotten to this point. It&#8217;s a depressing thing to think about really; had Microsoft just done things right the first time (or at the very least come out with hot fixes to make the needed changes) we wouldn&#8217;t be in this mess to begin with. People are always complaining about IE, more so since browsers like Firefox have stepped into the ring. I&#8217;m aware that Firefox is not perfect, but that&#8217;s not what I&#8217;m arguing. Firefox, along with the other browsers, took far more time to correct CSS bugs than IE ever did. Only now with the eventual release of IE 8 are we looking at IE possibly coming up par.</p>
<p></p>
<p>I don&#8217;t work on the team, and I&#8217;m truly glad I don&#8217;t. These guys are basically the internet pariah group of the century. Everyone can hate IE with little to no effort due to its historic record of screwing up websites. I&#8217;m glad to see that they&#8217;re working so hard to get the browser up to speed on the compliance front, as well as trying to make it easier for everyone. Sadly, by making it easier for everyone they really hurt further progression in the field.</p>
<p>Allowing HTML writers to slap a version on their site and let it be that, you stifle the drive to improve their craft. You allow the user to literally say &#8220;good &#8217;nuff&#8221; to their work, and since the Web isn&#8217;t going away anytime soon, I shudder to think of what will become of the next generation of web designers. It&#8217;s going to be the Geocities site builder circa 1997 all over again.</p>
<p>I guess it would at least look the same in every browser, so that&#8217;s something. In the end I&#8217;m against the idea from a progression standpoint, but I have to admit &#8211; if not begrudgingly &#8211; that at least this would stop sites from breaking every release. It&#8217;s gross, but it&#8217;d work.</p>
<p>P.S. <a href="http://www.katemonkey.co.uk/article/48/x-ua-lemur-compatible?commented=1#c000079" title="Katemonkey" target="_blank">This</a> is the greatest summary of the issue, bar none.</p>
]]></content:encoded>
			<wfw:commentRss>http://wallofscribbles.com/2008/apparently-ie8-is-causing-ruckus/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

