Just adding my $0.02 about why browser sniffing should be discouraged
but never completely deprecated -
I use browser sniffing to redefine the fadeIn/fadeOut effects to
slideDown/slideUp for IE7, because of the ClearType issue. It's a case
where the effect _works_, so I can't use feature detection, but since
the opacity animation effects look awful, it's not realistic to use
those effects in IE7. As far as I can tell, it's a case where browser
sniffing is still the best option.
if ($.browser.msie) {
jQuery.fn.fadeOut = jQuery.fn.slideUp;
jQuery.fn.fadeIn = jQuery.fn.slideDown;
}
(I know I *should* be testing for IE version ... but then again it
wouldn't surprise me at all if the ClearType problem persists in IE8)
-Wick
http://www.CarComplaints.com
On Feb 5, 5:45 am, Liam Potter <radioactiv...@gmail.com> wrote:
> I'm doing this because every now and then safari seems to have a spasm
> with something, and the css hacks for safari are shoddy at best.
>
> Klaus Hartl wrote:
> >> I know it still works in 1.3, just wondering why we are advised not to
> >> use it.
>
> > Because feature detection is much more future proof and stable than
> > browser sniffing. With browser sniffing you simply make wrong
> > assumptions.
>
> > CSS may be a different beast, although I've never had the need for an
> > extra style sheet other than IE, which I include with Conditional
> > Comments.
>
> > --Klaus
