Yesterday, the jQuery official website released the jQuery 1.8 Release version, which is now available on the official website: http://jquery.com/.
Since I haven’t found any articles on this topic yet, I’ll give you a brief introduction (Note: This article is just a brief summary, not a complete translation. For the full text, please refer to the original text: http: //blog.jquery.com/2012/08/09/jquery-1-8-released/).
1. Code acquisition
http://code.jquery.com/jquery-1.8.0.min.js (Compressed version, recommended for production environments)
http://code.jquery.com/jquery-1.8.0.js (Source code version, recommended for debugging and research)
2. Main changes
1. Refactor the selector (Sizzle) engine: The sizzle engine is now faster than before. This should give priority to the querySelectorAll feature that many browsers now support. Additionally :has() and :contains() still support IE6/7.
2. Animation: The previously existing animations are still supported. The main change this time is to reorganize the previous code and enhance some functions.
3. Better support for prefixes in CSS: For example, use .css("user-select", "none"); the value in Chromw/Safari is "-webkit-user-select", The value in Firefox is "-moz-user-select" and in IE10 it is "-ms-user-select".
4. The $(html, props) method is more flexible.
5. More than 160 bugs have been fixed.
6. The code is further reduced: the compressed code file is hundreds of bytes smaller than version 1.7.2.
7. Modularization: If you clearly know the dependencies of jQuery in the project, you can remove the unnecessary parts. The module version is just the beginning, and later versions will have better support.
3. Removed parts
Simply put, for the sake of transition, there are very few parts removed in this version. The following are the removed parts (all used less):
1. $(element).data("events")
2. Deferred.isResolved() and Deferred.isRejected ()
3. $(element).closest(Array) returns Array
4. $.curCSS
5. $.attrFn
four , Report bug
If you find a bug, you can first go to jsFiddle or jsbin to create a test case, and then submit it to jQuery bug tracker.
If you are not sure whether this is a bug, you can ask questions on the jQuery official forum: http://forum.jquery.com/