On Jan 14, 8:45 am, John Resig <jere...@gmail.com> wrote: > jQuery 1.3 is out!
Fantastic! There is definite improvement here. Now I just need to do a bunch of testing to work it into some existing apps and benefit from the performance increases. One of the common criticisms of jQuery has been the browser sniffing, and I'm happy that feature testing is now being used. But I'm concerned about how it's implemented. It seems backwards to me in some cases. For example, opacity. The "support" check is whether style.opacity works correctly, but if it doesn't then it is _assumed_ that using alpha is the fix. This is the wrong logic. Instead, you should check specifically for whether alpha is required. A browser may exist (in theory) that doesn't support style.opacity or alpha, and needs some other fix. Same thing with cssFloat vs. styleFloat or style vs. cssText, etc. You should be testing for non-standard functionality, not testing for the standard behavior and if it's not correct then assuming what the fix should be. Is there any reason feature detection was implemented in this way? 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 -~----------~----~----~----~------~----~------~--~---
