On Jan 14, 3:11 pm, "David Zhou" <da...@nodnod.net> wrote:
> A new browser to be support would be enough to warrant a new version
> of jQuery, I think.  

Which would be entirely unnecessary if feature detection is done
correctly and the new browser doesn't have any bugs to account for.

> In terms of logic, I think it definitely makes sense to test for
> standards support *first* and then fall back.  This (rightly, I think)
> assumes that over time browsers will get *more* compliant.

Perhaps, but jQuery has the potential to support browsers like those
in phones and other obscure agents that may not be common. It doesn't
_need_ to limit its browser support to such a small subset if it would
just handle things correctly. As people move towards more mobile apps,
wouldn't it be great if jQuery continued to work in that environment?
Or when Chrome is released, it could be assumed that it worked
correctly until/unless there are specific quirks to fix?

> If there's ever a case where a third condition arises, it'd be
> relatively trivial to do:
> if supports_ standard
>      standard
> else if supports_other_method
>      other_method
> else
>      other_method2

Why would you want to make the assumption that if a browser doesn't
support the standards way or the other_method, that it must support
other_method2? Without ever checking if it really does support
other_method2? That is logically error-prone. If a browser update is
released with a bug that breaks the standards approach, you wouldn't
want to then apply a fix that is meant for an entirely different
browser, would you? If FF 3.2 breaks "opacity" (for some strange
reason, in theory), why would you then want to apply the IE fix of
using alpha? It makes no sense. It's the wrong logic!

These concepts have been around for a number of years and are used
often in robust, reliable, browser-agnostic applications. jQuery needs
to catch up with the times if it is to be taken more seriously as a
solid js framework. Again, IMO. And I am a jQuery user and advocate
(for the right situations), so I say this not because of some desire
to nit-pick or criticize, but because I want the js framework that I
use to be as solid as possible.

Matt Kruse

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to 
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to