<?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: Five simple steps to alleviate IE6 frustration</title>
	<atom:link href="http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/</link>
	<description>Thoughts on web development and technologies by Peter Gasston</description>
	<lastBuildDate>Mon, 06 Feb 2012 13:50:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Scott</title>
		<link>http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-24338</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Wed, 11 Feb 2009 19:39:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-24338</guid>
		<description>Too me using conditionals for IE6 or let alone 7 is a HACK!! 

We have finally decided to use a template/themeing strategy that already exists with our site and created a theme specifically for IE6. This allows us to change the DOM and CSS as we see fit for that evil browser instead of tying up resources trying to write utopia code for all. This has actually become more maintenance friendly for us instead of testing troublesome cascading conditionals and star hacks. Since in reality your already keeping track of two front ends anyway. (we are utilizing smarty .tpls for this)</description>
		<content:encoded><![CDATA[<p>Too me using conditionals for IE6 or let alone 7 is a HACK!! </p>
<p>We have finally decided to use a template/themeing strategy that already exists with our site and created a theme specifically for IE6. This allows us to change the DOM and CSS as we see fit for that evil browser instead of tying up resources trying to write utopia code for all. This has actually become more maintenance friendly for us instead of testing troublesome cascading conditionals and star hacks. Since in reality your already keeping track of two front ends anyway. (we are utilizing smarty .tpls for this)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-7122</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Wed, 30 Jan 2008 03:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-7122</guid>
		<description>Peter,

Agreed, a little info on all of IE&#039;s quirks will get you most of the way there, but the sheer number of bugs at all levels (HTML, CSS, DOM, JS) is just astounding sometimes, and I doubt that anyone has a complete list of all the bugs/issues with IE.

I&#039;ve started my own collection of the most frustrating here (for all browsers), but alas 90% of them are for IE.

Example query:
http://webbugtrack.blogspot.com/search/label/DOM%20Methods</description>
		<content:encoded><![CDATA[<p>Peter,</p>
<p>Agreed, a little info on all of IE’s quirks will get you most of the way there, but the sheer number of bugs at all levels (HTML, CSS, DOM, JS) is just astounding sometimes, and I doubt that anyone has a complete list of all the bugs/issues with IE.</p>
<p>I’ve started my own collection of the most frustrating here (for all browsers), but alas 90% of them are for IE.</p>
<p>Example query:<br />
<a href="http://webbugtrack.blogspot.com/search/label/DOM%20Methods" rel="nofollow">http://webbugtrack.blogspot.com/search/label/DOM%20Methods</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Website maken</title>
		<link>http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-3060</link>
		<dc:creator>Website maken</dc:creator>
		<pubDate>Sat, 27 Oct 2007 01:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-3060</guid>
		<description>I don&#039;t know why Microsoft released IE7, it&#039;s 100% frustration for webmasters. We have to change our html every time and it looks different in every browser. Shame shame Microsoft!</description>
		<content:encoded><![CDATA[<p>I don’t know why Microsoft released IE7, it’s 100% frustration for webmasters. We have to change our html every time and it looks different in every browser. Shame shame Microsoft!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaap</title>
		<link>http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-686</link>
		<dc:creator>Jaap</dc:creator>
		<pubDate>Thu, 09 Aug 2007 15:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-686</guid>
		<description>I agree 100%... if you know the most common bugs and their workarounds a lot is possible. It&#039;s annoying that advanced selectors are missing but those can often times be worked around by using special class names.

Also, if you keep your layouts fixed getting IE(6) to behave is a lot easier. But I must say, point 4 is the most useful but also the hardest one.</description>
		<content:encoded><![CDATA[<p>I agree 100%… if you know the most common bugs and their workarounds a lot is possible. It’s annoying that advanced selectors are missing but those can often times be worked around by using special class names.</p>
<p>Also, if you keep your layouts fixed getting IE(6) to behave is a lot easier. But I must say, point 4 is the most useful but also the hardest one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-674</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 09 Aug 2007 07:25:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-674</guid>
		<description>IE6 supports the use of &#039;margin: 0 auto&#039;. I&#039;m using it on this site, for example.</description>
		<content:encoded><![CDATA[<p>IE6 supports the use of ‘margin: 0 auto’. I’m using it on this site, for example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Navarr</title>
		<link>http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-669</link>
		<dc:creator>Navarr</dc:creator>
		<pubDate>Thu, 09 Aug 2007 00:34:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.broken-links.com/2007/08/09/four-simple-steps-to-alleviate-ie6-frustration/#comment-669</guid>
		<description>The problem is that IE6, and hell even IE7 doesn&#039;t support all of CSS2!!!!

When we have to add things like &quot;text-align:center;&quot; to a previous box element just to get another box element to center when we could, logically use &quot;margin: 0 auto;&quot;.

And of course; lets not even go into CSS3.

IE could use a lot of improvement with doing things the ways STANDARDS say things should be done.

* { display: relative; } shows such things.</description>
		<content:encoded><![CDATA[<p>The problem is that IE6, and hell even IE7 doesn’t support all of CSS2!!!!</p>
<p>When we have to add things like “text-align:center;” to a previous box element just to get another box element to center when we could, logically use “margin: 0 auto;”.</p>
<p>And of course; lets not even go into CSS3.</p>
<p>IE could use a lot of improvement with doing things the ways STANDARDS say things should be done.</p>
<p>* { display: relative; } shows such things.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

