<?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: A new answer to the IE6 question?</title>
	<atom:link href="http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/</link>
	<description>Web design news and insights since 1995</description>
	<lastBuildDate>Fri, 19 Mar 2010 14:24:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Walls Come Tumbling Down presentation slides and transcript &#124; Stuff and Nonsense</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-51204</link>
		<dc:creator>Walls Come Tumbling Down presentation slides and transcript &#124; Stuff and Nonsense</dc:creator>
		<pubDate>Fri, 25 Dec 2009 03:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-51204</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Instead I provide simple but effectively designed HTML elements. This means great typography for headings, paragraphs, quotations, lists, tables and forms and no styling of layout. I think that Universal Internet Explorer 6 CSS pushes all the right buttons as a concept, but I know that it won&#039;t be appropriate in every situation. That&#039;s for you and your clients to judge. As Jeffrey Zeldman wrote in response: [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Instead I provide simple but effectively designed HTML elements. This means great typography for headings, paragraphs, quotations, lists, tables and forms and no styling of layout. I think that Universal Internet Explorer 6 CSS pushes all the right buttons as a concept, but I know that it won&#39;t be appropriate in every situation. That&#39;s for you and your clients to judge. As Jeffrey Zeldman wrote in response: [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Universal Internet Explorer 6 CSS &#124; For A Beautiful Web</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-43815</link>
		<dc:creator>Universal Internet Explorer 6 CSS &#124; For A Beautiful Web</dc:creator>
		<pubDate>Wed, 01 Jul 2009 20:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-43815</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] As Jeffrey rightly pointed out in his commentary, “ No hammer fits all nails, and no solution, however elegant, will work for every situation. But [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] As Jeffrey rightly pointed out in his commentary, “ No hammer fits all nails, and no solution, however elegant, will work for every situation. But [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet Explorer 6 compatibility &#171; Brad Bice &#8211; professional portfolio, projects and examples</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-43530</link>
		<dc:creator>Internet Explorer 6 compatibility &#171; Brad Bice &#8211; professional portfolio, projects and examples</dc:creator>
		<pubDate>Thu, 18 Jun 2009 20:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-43530</guid>
		<description>[...] Jeffrey Zeldman said when referring to Clarke&#8217;s method, &#8220;no solution, however elegant, will work for every situation.&#8221; But work like this will [...]</description>
		<content:encoded><![CDATA[<p>[...] Jeffrey Zeldman said when referring to Clarke&#8217;s method, &#8220;no solution, however elegant, will work for every situation.&#8221; But work like this will [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Javascript Tool Takes Aim At Web-Site Readability</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-43147</link>
		<dc:creator>New Javascript Tool Takes Aim At Web-Site Readability</dc:creator>
		<pubDate>Mon, 08 Jun 2009 22:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-43147</guid>
		<description>[...] &#8220;Readability&#8221;. Recently, on web-standards guru Jeffrey Zeldman&#8217;s blog there was a  post which mentions briefly, in passing, &#8220;Arc90&#8217;s awesome Readability plug-in&#8221;. A [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Readability&#8221;. Recently, on web-standards guru Jeffrey Zeldman&#8217;s blog there was a  post which mentions briefly, in passing, &#8220;Arc90&#8217;s awesome Readability plug-in&#8221;. A [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thunderlizard Digest</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42895</link>
		<dc:creator>Thunderlizard Digest</dc:creator>
		<pubDate>Tue, 02 Jun 2009 21:43:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42895</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] of people are still using older browsers, including Internet Explorer 6. The great Jeffrey Zeldman writes about Andy Clarke&#039;s cool solution to dealing with CSS problems in IE6. At Web Design World, you can learn [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] of people are still using older browsers, including Internet Explorer 6. The great Jeffrey Zeldman writes about Andy Clarke&#8217;s cool solution to dealing with CSS problems in IE6. At Web Design World, you can learn [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keronsen's Bookmarks on Delicious</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42841</link>
		<dc:creator>keronsen's Bookmarks on Delicious</dc:creator>
		<pubDate>Mon, 01 Jun 2009 11:23:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42841</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Jeffrey Zeldman Presents : A new answer to the IE6 question? SAVE [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Jeffrey Zeldman Presents : A new answer to the IE6 question? SAVE [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Universal IE6 CSS and memories of NS4 - MeganMcDermott.com</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42827</link>
		<dc:creator>Universal IE6 CSS and memories of NS4 - MeganMcDermott.com</dc:creator>
		<pubDate>Sat, 30 May 2009 03:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42827</guid>
		<description>[...] as Zeldman notes: No hammer fits all nails, and no solution, however elegant, will work for every situation. [...]</description>
		<content:encoded><![CDATA[<p>[...] as Zeldman notes: No hammer fits all nails, and no solution, however elegant, will work for every situation. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brent Friar</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42826</link>
		<dc:creator>Brent Friar</dc:creator>
		<pubDate>Sat, 30 May 2009 00:51:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42826</guid>
		<description>As much as I hate IE6 and as often as I threaten to drop support, I still find myself putting in the fixes. Seriously, how hard is it to serve up a small CSS file wilh the necessary hacks to fix the design enough to make is passable in IE6? I rarely have more than a dozen lines of CSS is that in the IE6 only file.

All of the IE6 CSS bugs and fixes are well documented. Not implementing them is just lazy.</description>
		<content:encoded><![CDATA[<p>As much as I hate IE6 and as often as I threaten to drop support, I still find myself putting in the fixes. Seriously, how hard is it to serve up a small CSS file wilh the necessary hacks to fix the design enough to make is passable in IE6? I rarely have more than a dozen lines of CSS is that in the IE6 only file.</p>
<p>All of the IE6 CSS bugs and fixes are well documented. Not implementing them is just lazy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos Eduardo</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42819</link>
		<dc:creator>Carlos Eduardo</dc:creator>
		<pubDate>Fri, 29 May 2009 13:29:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42819</guid>
		<description>It&#039;s a good approach, but I think it cannot resolve our problems with IE6. We can consider it like &quot;graceful degradation&quot; ?

After working some years with so many clients I know that we can&#039;t ignore IE6, &#039;cause most of their clients are using IE (at least IE6) and we can&#039;t deliver something that doesn&#039;t fills their expectation about layout, no matter what browser are you using.

So this is a good choice to use it in a personal site, but when you are working for clients, you can&#039;t ignore so many users that uses IE6 yet... Sadly...</description>
		<content:encoded><![CDATA[<p>It&#8217;s a good approach, but I think it cannot resolve our problems with IE6. We can consider it like &#8220;graceful degradation&#8221; ?</p>
<p>After working some years with so many clients I know that we can&#8217;t ignore IE6, &#8217;cause most of their clients are using IE (at least IE6) and we can&#8217;t deliver something that doesn&#8217;t fills their expectation about layout, no matter what browser are you using.</p>
<p>So this is a good choice to use it in a personal site, but when you are working for clients, you can&#8217;t ignore so many users that uses IE6 yet&#8230; Sadly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stevie D</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42788</link>
		<dc:creator>Stevie D</dc:creator>
		<pubDate>Thu, 28 May 2009 11:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42788</guid>
		<description>&lt;blockquote&gt;If you tell a client it costs $X more for the site to work in IE6, and they still want it, fine, extra money for the extra time. But I find that often this leads to them jumping on board the death to IE6 campaign.&lt;/blockquote&gt;
That&#039;s all very well, but do you explain that by doing that, they are writing off about 15% of potential customers from the word go?
&lt;blockquote&gt;Anyway, I think that ie 6 will die quite soon, not because of ie8, but because companies that still run win 2000 or even nt might drop theses OSes for Seven.&lt;/blockquote&gt;
I&#039;d like to think so, but I work for a company running 2000 and I don&#039;t see it happening in the next year at least :-(
&lt;blockquote&gt;Also, imagine someone sees a webpage at a friend’s. He opens his ie6 at home and gets a different page. Initial reaction: wrong url.&lt;/blockquote&gt;
You could easily modify the CSS to include &lt;em&gt;some&lt;/em&gt; level of site branding, eg a logo and colour. You could also put a box at the top: &quot;Not the page you were expecting? You&#039;re on the right website, but it&#039;s displayed differently because you&#039;re using an old browser. &lt;a href=&quot;#&quot; rel=&quot;nofollow&quot;&gt;Find out more...&lt;/a&gt;&quot; kind of thing. Not an obtrusive thing, just an info box to help people understand they are in the right place and why they aren&#039;t getting quite the full experience.</description>
		<content:encoded><![CDATA[<blockquote><p>If you tell a client it costs $X more for the site to work in IE6, and they still want it, fine, extra money for the extra time. But I find that often this leads to them jumping on board the death to IE6 campaign.</p></blockquote>
<p>That&#8217;s all very well, but do you explain that by doing that, they are writing off about 15% of potential customers from the word go?</p>
<blockquote><p>Anyway, I think that ie 6 will die quite soon, not because of ie8, but because companies that still run win 2000 or even nt might drop theses OSes for Seven.</p></blockquote>
<p>I&#8217;d like to think so, but I work for a company running 2000 and I don&#8217;t see it happening in the next year at least :-(</p>
<blockquote><p>Also, imagine someone sees a webpage at a friend’s. He opens his ie6 at home and gets a different page. Initial reaction: wrong url.</p></blockquote>
<p>You could easily modify the CSS to include <em>some</em> level of site branding, eg a logo and colour. You could also put a box at the top: &#8220;Not the page you were expecting? You&#8217;re on the right website, but it&#8217;s displayed differently because you&#8217;re using an old browser. <a href="#" rel="nofollow">Find out more&#8230;</a>&#8221; kind of thing. Not an obtrusive thing, just an info box to help people understand they are in the right place and why they aren&#8217;t getting quite the full experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ara Pehlivanian</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42752</link>
		<dc:creator>Ara Pehlivanian</dc:creator>
		<pubDate>Tue, 26 May 2009 15:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42752</guid>
		<description>P.S.: A quick look at the ie6 css file reveals some glaring problems when it comes to performance. Using expressions are a big no no as the browser recalculates values at every mousemove event, likewise the fact that no CSS hacks are being used means the file will likely be loaded via conditional comments, yet another HTTP request. It&#039;s nice in theory, but again, way too much bending over backwards for a backwards browser.</description>
		<content:encoded><![CDATA[<p>P.S.: A quick look at the ie6 css file reveals some glaring problems when it comes to performance. Using expressions are a big no no as the browser recalculates values at every mousemove event, likewise the fact that no CSS hacks are being used means the file will likely be loaded via conditional comments, yet another HTTP request. It&#8217;s nice in theory, but again, way too much bending over backwards for a backwards browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ara Pehlivanian</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42750</link>
		<dc:creator>Ara Pehlivanian</dc:creator>
		<pubDate>Tue, 26 May 2009 15:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42750</guid>
		<description>Meh. I&#039;m through bending over backwards for an 8 year old browser that&#039;s two versions behind. People need to start feeling the pain of navigating the web with that kludge and go upgrade. If it&#039;s IT departments, then their users need to start complaining. Enough with IE6.</description>
		<content:encoded><![CDATA[<p>Meh. I&#8217;m through bending over backwards for an 8 year old browser that&#8217;s two versions behind. People need to start feeling the pain of navigating the web with that kludge and go upgrade. If it&#8217;s IT departments, then their users need to start complaining. Enough with IE6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maaike</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42724</link>
		<dc:creator>Maaike</dc:creator>
		<pubDate>Mon, 25 May 2009 11:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42724</guid>
		<description>I totally agree with &lt;a href=&quot;http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42611&quot; rel=&quot;nofollow&quot;&gt;Niels&lt;/a&gt;. It doesn&#039;t rock, it&#039;s bad usability. I think progressive enhancement is the best way to go.</description>
		<content:encoded><![CDATA[<p>I totally agree with <a href="http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42611" rel="nofollow">Niels</a>. It doesn&#8217;t rock, it&#8217;s bad usability. I think progressive enhancement is the best way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Javascript Tool Takes Aim At Web-Site Readability &#171; ReadableWeb</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42717</link>
		<dc:creator>New Javascript Tool Takes Aim At Web-Site Readability &#171; ReadableWeb</dc:creator>
		<pubDate>Mon, 25 May 2009 00:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42717</guid>
		<description>[...] &#8220;Readability&#8221;. Recently, on web-standards guru Jeffrey Zeldman&#8217;s blog there was a  post which mentions briefly, in passing, &#8220;Arc90&#8217;s awesome Readability plug-in&#8221;. A [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Readability&#8221;. Recently, on web-standards guru Jeffrey Zeldman&#8217;s blog there was a  post which mentions briefly, in passing, &#8220;Arc90&#8217;s awesome Readability plug-in&#8221;. A [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Fink</title>
		<link>http://www.zeldman.com/2009/05/21/a-new-answer-to-the-ie6-question/#comment-42697</link>
		<dc:creator>Richard Fink</dc:creator>
		<pubDate>Sun, 24 May 2009 08:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1140#comment-42697</guid>
		<description>Does not rock. Premature, but bookmarked.</description>
		<content:encoded><![CDATA[<p>Does not rock. Premature, but bookmarked.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
