<?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: Universal IE6 CSS &#8211; With Caution</title>
	<atom:link href="http://www.acquiweb.com/blog/index.php/2009/05/22/universal-ie6-css-with-caution/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.acquiweb.com/blog/index.php/2009/05/22/universal-ie6-css-with-caution/</link>
	<description></description>
	<lastBuildDate>Mon, 08 Aug 2011 20:55:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Darren</title>
		<link>http://www.acquiweb.com/blog/index.php/2009/05/22/universal-ie6-css-with-caution/comment-page-1/#comment-2373</link>
		<dc:creator>Darren</dc:creator>
		<pubDate>Tue, 30 Jun 2009 13:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.acquiweb.com/blog/?p=77#comment-2373</guid>
		<description>Hi Andy, thanks for your feedback. Just to clarify one thing before I respond, I don&#039;t work for an agency, I manage the central web team in the NI Civil Service. Any policies in place to cater for any specific users come from my team and are backed up with good reasoning.
With reflection my original post was more militant that originally intended but I still think the point I tried to convey is valid. In the NICS we have valid reasons for using IE6 and its so complicated I couldn&#039;t begin to explain without wearing my fingers out. Regardless of what I or anyone else thinks of IE6, if my user base is significant then I think we are right to cater for IE6 users as much as possible. A &quot;Universal&quot; stylesheet is not acceptable in my opinion and I guess it&#039;s this misleading name that I take exception to. Yes there may times in the private sector when it&#039;s ok to serve this stylesheet up and not cost effective to spend additional hours developing for IE6 but a Universal solution? Surely not? Only when appropriate to do so IE6 CSS would be a much catchier name!</description>
		<content:encoded><![CDATA[<p>Hi Andy, thanks for your feedback. Just to clarify one thing before I respond, I don&#8217;t work for an agency, I manage the central web team in the NI Civil Service. Any policies in place to cater for any specific users come from my team and are backed up with good reasoning.<br />
With reflection my original post was more militant that originally intended but I still think the point I tried to convey is valid. In the NICS we have valid reasons for using IE6 and its so complicated I couldn&#8217;t begin to explain without wearing my fingers out. Regardless of what I or anyone else thinks of IE6, if my user base is significant then I think we are right to cater for IE6 users as much as possible. A &#8220;Universal&#8221; stylesheet is not acceptable in my opinion and I guess it&#8217;s this misleading name that I take exception to. Yes there may times in the private sector when it&#8217;s ok to serve this stylesheet up and not cost effective to spend additional hours developing for IE6 but a Universal solution? Surely not? Only when appropriate to do so IE6 CSS would be a much catchier name!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.acquiweb.com/blog/index.php/2009/05/22/universal-ie6-css-with-caution/comment-page-1/#comment-2372</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 29 Jun 2009 21:44:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.acquiweb.com/blog/?p=77#comment-2372</guid>
		<description>Interesting. It seems from your article that you work for an agency who are forcing employees to use IE6 which even Microsoft have stopped supporting. As such, your employers have a policy of developing for it. 
I don&#039;t think your post really addresses the problem being discussed though.
Your argument seems to be that even though nobody wants to pay to support IE6 (not Microsoft, not clients and not the people who refuse to stop using it) developers should still go ahead and do so. This is just the tip of the iceberg of course, supporting IE generally but especially version 6 inherently means a departure from web standards in most cases. As a freelancer myself, supporting IE6 goes at the bottom of a long list of priorities that many clients are stretching to pay for including (but not limited to and in no particular order) accessibility, seo, photography and illustration. You aren&#039;t alone of course, there are still people moaning about lack of support for ie5.
Thanks for a stimulating post!</description>
		<content:encoded><![CDATA[<p>Interesting. It seems from your article that you work for an agency who are forcing employees to use IE6 which even Microsoft have stopped supporting. As such, your employers have a policy of developing for it.<br />
I don&#8217;t think your post really addresses the problem being discussed though.<br />
Your argument seems to be that even though nobody wants to pay to support IE6 (not Microsoft, not clients and not the people who refuse to stop using it) developers should still go ahead and do so. This is just the tip of the iceberg of course, supporting IE generally but especially version 6 inherently means a departure from web standards in most cases. As a freelancer myself, supporting IE6 goes at the bottom of a long list of priorities that many clients are stretching to pay for including (but not limited to and in no particular order) accessibility, seo, photography and illustration. You aren&#8217;t alone of course, there are still people moaning about lack of support for ie5.<br />
Thanks for a stimulating post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

