Monday, September 28, 2009

[jQuery] Re: Prevent jagged text in IE

deprecating the UA interrogation was a bad move imo, simply because
sometimes you legitimately want to know what browser somebody is
running, rather than whether it has support for feature-x. it takes 5
mins to write a function to find the browser/os/whatever (and five
seconds to copy/paste one you wrote previously ;-) ) but not having to
re-write that is very much the point of jquery.

a framework shouldn't dictate what you can do, but provide tools to do
it as efficiently as possible. checking for a combination of features
that you know are supported in the current version of chrome to find
that browser isn't particularly efficient both in terms of code and
maintenance.

as for the x-browser animation issue, i suspect (rightly or wrongly)
this would get filed away as an IE bug rather than a feature of
jquery.

On Sep 27, 8:09 pm, Kevin Dalman <kevin.dal...@gmail.com> wrote:
> If browser-detection can't be used, then subsititute code to detect
> the "filter" attribute instead. The exact syntax is not important...
>
> I believe jQuery SHOULD handle this cross-browser animation issue
> because it is common to the majority of users. It is clearly a
> deficiency when jQuery's own contributors have to override core
> methods to address it. The choices are:
>
>  A) Update jQuery to handle this issue natively, or;
>
>  B) Continue using hacks for animations in the world's most common
> browser.
>
> I'm interested in opinions on this, particularly from the regular
> jQuery contributors.
>
> /Kevin
>
> On Sep 27, 4:20 am, "ryan.j" <ryan.joyce...@googlemail.com> wrote:
>
> > browser sniffing is already deprecated in favour of feature sniffing,
> > it's unlikely code using it will be added.

No comments: