> I'm not sure why this 'fix' should be added to fadeOut? It seems most
> applicable to fadeIn and fadeTo.
Whoops, right. So the problem would be that in IE only, .fadeTo
("slow", 1) makes the element completely visible and then pops to 50%
opacity based on the stylesheet when the element's filter property is
removed.
> There is no way to fix anti-aliasing if the user *chooses* to use
> opacity since this is a browser issue,
If the user chooses to set a 50% opacity in the stylesheet that should
work properly in IE as well, right? A fix for antialiasing shouldn't
break something that currently works properly across browsers.
> Calling it an IE-bug doesn't make it go away. This is a cross
> browser issue, pure and simple.
If this problem has a good fix, it should be fixed. There are several
cases that will break differently in IE when this proposed fix is
applied. It's not achieving consistent cross-browser behavior. There
may be a solution out there still, and if someone has one they should
post it.
