Well, at least they made the amendment that showed the 2020 date is incorrect, but it hasn’t been confirmed.
What I do now is during my discovery phase, I ask specifically if they need IE6 support. I’ll make sure that the foundational template shows up fine in IE6, but I don’t support it beyond that unless the client specifically wants it.
Having a sweet reset usually addresses a lot of the issues with IE6 understanding of CSS
I’m glad someone else pointed this out, because this is so incredibly true. The vast majority of people who moan about IE6 completely screwing up their CSS do not use a reset stylesheet.
When I code websites I find myself having to make only one or 2 adjustments for IE6, normally just a couple of widths that need to be amended, but in reality there isn’t much CSS alteration needed if you are coding properly.
IE6’s support for modern web technologies is a problem though and this is the reason I cannot wait for it to die.
I Know it’s wrong but.. you get prompted so many times to update non stop so I choose to not develop for IE6
i hate having a working site JUST to have to tweek it around for IE6.. so if you live in a world of IE6 UPDATE your SOFTWARE.