@Dave
>
> with the "fix", fades out but then pops to 50% opacity
I'm not sure why this 'fix' should be added to fadeOut? It seems most
applicable to fadeIn and fadeTo. But whatever the case, a little extra
code could handle edge-cases -- something like...
if (jQuery.browser.msie && $(this).css('opacity')==1)
this.style.removeAttribute('filter')
Or for the politically correct...
var $E = $(this);
if ($E.css('filter') && $E.css('opacity')==1)
this.style.removeAttribute('filter')
There is no way to fix anti-aliasing if the user *chooses* to use
opacity since this is a browser issue, but it is *other 99%* that is
the issue. There are many 'effects' used in jQuery that trigger the
problem, so it should handle these *common scenarios*. Calling it an
IE-bug doesn't make it go away. This is a a cross browser issue, pure
and simple.
/Kevin
On Sep 29, 7:34 am, Dave Methvin <dave.meth...@gmail.com> wrote:
> > This is a nice simple solution to a common cross-browser issue, so
> > wouldn't it be reasonable for this to be added to the standard jQuery
> > animate method? The extra size is minimal.
>
> That solution assumes no opacity was specified in a stylesheet.
>
> <style>
> #glory {
> opacity: 0.5;
> filter: alpha(opacity = 50);
> }
> </style>
> <script>
> // with the "fix", fades out but then pops to 50% opacity
> $("#glory").fadeOut();
> </script>
