I know that IE (6 and 7) both have issues with opacity with regards to
content inside the opacity-changing container. If the content has bold
text (IE6 and 7) or transparent PNG images there can be display issues
- the font is rendered without it's anti-aliasing (eg. cleartype) and
the image is rendered without the transparent PNG support (IE6 and 7).
Try it yourself - put a <strong> tag inside a div along with a
transparent PNG and do a fadeTo on it. There are a fair few posts
covering this topic.
I'm not sure if that's the reason why they did it - it's the only
thing I can think of without looking at it closer.
On Sep 1, 10:37 pm, Feed <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> About the new jQuery website, you noticed that it has 3 blue links:
>
> - Lightweight Footprint
> - CSS3 Compliant
> - Cross-browser
>
> When you hover, it displays a box that stays above the link. I was
> looking into the code when I found this:
>
> //cta tooltips
> if($.browser.msie){
> $('div.jq-checkpointSubhead').hide();
>
> $('#jq-intro li').hover(
>
> function(){$(this).find('div.jq-checkpointSubhead').fadeIn(500);},
>
> function(){$(this).find('div.jq-checkpointSubhead').fadeOut(500);}
> );}else{
>
> $('div.jq-checkpointSubhead').hide().css({'opacity': 0.0001,
> 'display': 'block'});
>
> $('#jq-intro li').hover(
>
> function(){$(this).find('div.jq-checkpointSubhead').fadeTo(500,
> 0.9999);},
>
> function(){$(this).find('div.jq-checkpointSubhead').fadeTo(500,
> 0.0001);}
> );
>
> }
>
> Now, my question is: why they used a $.browser.msie detection to make
> the event different in IE? Why not use the same code for all browsers?
> Is there a bug in fadeIn/fadeOut, or maybe fadeTo?
