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 detectio
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
> 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
I know it still works in 1.3, just wondering why we are advised not to
use it.
Mauricio (Maujor) Samy Silva wrote:
Liam,
Quoting the documentation:
"It's important to note that jQuery.browser is still in jQuery - and
will be for the foreseeable future (too many plugins and pieces of
code d
Liam,
Quoting the documentation:
"It's important to note that jQuery.browser is still in jQuery - and will be
for the foreseeable future (too many plugins and pieces of code depend on
it)."
Read the full section at:
http://docs.jquery.com/Release:jQuery_1.3#No_More_Browser_Sniffing
MaurĂcio
5 matches
Mail list logo