As much as a part of me would like to see that happen, that'd really be an odd precedent -- not just <i>not</i> going out of their way to continue making something work on an older buggy browser but actively blocking it from working when, presumably, it otherwise would. I'd be happy for them to pull any extra hacks/workarounds though and make the IE6 experience worse.