If you only need to support modern browsers and use their natively supported animations, you can skip the animation module entirely. Animation is work in progress. Sizzle, jQuery's CSS selector engine, has undergone a major rewrite in 1. This has brought performance improvements on selector matching, as well as improved shortcuts for the most common selectors. This creates an inefficient special case, so this behavior will be deprecated in jQuery 1.
Developers have sometimes forgotten this, passing strings to jQuery that come from untrustworthy sources which can lead to cross-site-scripting XSS attacks. In jQuery 1. Other options include using the jQuery 1. This function creates a new copy of jQuery whose properties and methods can be modified without affecting the original jQuery object. This hasn't proved to be useful and will be moved to the 1.
Expect the file size of jQuery 1. Here is what's planned for version 2. The goal is for 1. You can also use conditional comments to include 1. The jQuery team will continue to support and maintain version 1. The jQuery team doesn't anticipate adding a lot of new APIs in the future and new functionality will be added through plug-ins compatible with both 1. For more information, read jQuery 1. Join a community of over , senior developers.
View an example. You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered. Once you fix the warnings you can remove it. Or, leave the plugin in place until you have the chance to fix your code and plugins to make them 1.
Many thanks to those of you who reported bugs, and to the following people who contributed patches to the 1. Gold-leaf-cluster thanks to Paul Irish, who mobilized special forces to find a solution for ! Plugin authors should switch to more reliable feature detection instead of relying on browser sniffs. Lee: your example still sounds like something that could be replaced with feature sniffing.
Your website does not support IE because IE does not support certain things, right? As mentioned above, you people should try something like Modernizr and detect actual features instead of plain blocking which is bad and you should feel bad of specific browsers. Adeel: thanks! I saw it. I am giving a reason for its inclusion in jQuery itself, emphasizing that this feature is something other than just a poor replacement for feature detecting.
If the jQuery team wants to reorganize or rethink their code and they keep doing it , then having fewer things to worry about speeds things up. And as always, you are welcome to put browser detection back via jQuery Migrate, using the older version, the gist from Adeel above, checking navigator. IE version where all versions would return true if version is not passed in… :.
Thank you for continuing to trim the fat on this awesome JavaScript library! There are many options to get it back and it IS a poor way to do what most people use it for. Some versions of chrome that have the transitionend event it is unreliably implemented i.
With so many new features making their way into browsers along with a couple of bugs like the above example, i am not sure how you would feature detect this inadequacies. To detect the bug found by Christian might also be similar and unreliable or will involve triggering events and possibly replicating human behaviour to find the bug.
Is this overkill and hit website performance if the browser and version number are known? This was because an element was not getting focus in Firefox on page load when it was in other browsers. The jQuery Migrate plugin warns about it. Did you read the guide or use the plugin? If not, why? This is especially true for mobile development where feature detection is often just not enough.
It will also detect retina-like displays, touch events and even OS version. On top of that it has built in but optional functionality of loading scripts e. It takes a lot to write something so robust and yet give it away for free! Hands down you guys are the best may God bless you more! There is a version of jQuery available that supports all your needs.
View All 12 Subscribers. There were a lot of changes in 1. Reference bz Related Objects. Event Timeline. Reedy created this task. Krinkle added a comment. Change-Id: Iabdbc7cddafcd9fc99a0accab7ab5 When I tried this locally I got several uncaught exceptions.
One of them highlighted here consider this a blocker for upgrading to jquery 1. Aklapper added a comment. Bug has been marked as a duplicate of this bug. Reedy added a comment. Nothing we can't handle, but we need to: Fix core and all extensions at least the wmf-deployed ones, and leave release notes for others Announce on wikitech-ambassadors and elsewhere about these changes and give them a bit of time to check their stuff and fixup where needed.
No need for a separate bug. Jdforrester-WMF added a comment. Related patch-set: Remove jQuery. Garr, please ignore the last comment. Was already covered in comment RandomDSdevel awarded a token. Jdlrobson added a subscriber: Jdlrobson.
0コメント