On Fri, Feb 20, 2009 at 5:19 AM, Thomas Dalton thomas.dalton@gmail.com wrote:
There are different levels of support. We should certainly make sure things fail gracefully for IE6, but a new feature not working on IE6 shouldn't be a reason not to implement it for everyone else. (I believe that is pretty much the current policy already.)
It depends on the type of feature. For instance, when implementing different icons for certain filetypes on external links in Monobook, I used the [$=foo] CSS selector, knowing it would fail in IE6, because it's not going to hurt anyone if it does. On the other hand, it would still be unacceptable at this point for a significant new feature not to work in IE6. It still has 20% of the market, by some figures I've seen.