Call for jQuery 1.8 Ideas

We’re ready for our next round of community input, this time for version 1.8! This is your chance to suggest things we can fix, add, change, or remove in jQuery to make it better.

You can add a suggestion using this form; whenever possible provide links to a bug report, a page with a detailed description, or implementations that represent your idea. We’d like to have all your input by December 5 so we can read and discuss them before setting the 1.8 roadmap.

Many thanks for the suggestions left on our earlier blog post about how we can improve jQuery by trimming it down. We’ve gone through those comments and have a few thoughts about how we can address some of them in future versions.

Create a configurable download builder

Several people wondered why we don’t have a way to build a file with just the parts of jQuery you need, since jQuery UI, for example, has that option. It’s not quite the same situation. You know if you are using, say UI Accordion because you call it directly. You often do not know if you or some plugin you include on your page is using $.fn.prepend() or $.fn.animate(). Whether you are using them may even depend on parameters you pass to plugins at runtime.

To keep jQuery development manageable and ensure that CDNs can offer a single file that everyone on the Internet can share and cache effectively, the team wants to stay with a single file as its primary offering. Creating a configurable download may improve file size marginally, but it also complicates documentation, plugin use, and debugging. That is a lot more work for both you and us.

We’re already beginning the efforts to improve modularity by eliminating unwanted dependencies inside jQuery; many of the deprecated features we announce will be directed towards removing those dependencies. By laying that groundwork, others who want to create their own smaller subsets of jQuery or modular versions should have a much easier job.

However, we believe we can do even better than that, and would like to offer automated ways for any user to create an optimally minimized file that includes both application code and just the needed parts of jQuery. In particular, we are working with the Google Closure Compiler team to see if we could use its ADVANCED_OPTIMIZATIONS option. We’ll have more information on our progress as it develops.

Wait until version 2.0 before removing things

We’re sensitive to breaking all the existing jQuery code out there. That is why we are deprecating things as early as possible, so that people have plenty of time to change their code. Just because we deprecate something today, it does not necessarily mean we’ll remove it in the next version. We believe the list of things actually being removed in 1.8 are minor and unlikely to affect most users.

If our experiments with Closure Compiler pan out, we may even be able to leave in many deprecated features but they will be automatically removed if you don’t use them and build a custom application file that includes jQuery. That would be the best of both worlds.

Remove IE 6, 7, and/or 8 support

This topic comes up constantly, so let’s try to put it to bed once and for all. People tend to greatly overestimate the amount of code in jQuery that is specifically related to IE. Most of the problems in IE 6 and IE 7 are also present in IE 8, so there is no real size or complexity benefit to dropping support for the first two as long as that last one still has appreciable desktop market share and must be supported. Nobody (including Microsoft itself) likes these Jurassic Park browsers, but stripping out support for them right now would break web sites for many users.

That said, we know that older-IE support is not required in some scenarios such as mobile browsers. We are looking into ways to put as much of that code as possible into a single clearly marked block so that it can be easily removed by someone who is willing to create their own custom jQuery version. It may also be possible to get Closure Compiler’s help with this issue as well. However, we are not sure that will even provide a significant space savings in gzipped file size, and it won’t offer a performance boost since those code paths aren’t taken in other browsers.

Remove jQuery.browser

We have documented for nearly two years that we intend to move jQuery.browser into a plugin, and several people suggested it in the comments as well. Browser sniffing is not a reliable way to look for features, we recommend something like Modernizr instead. The regular expressions used for browser sniffing are large and don’t compress well; moving it to a plugin will ensure that only the people who use it must pay that size penalty.

What about your ideas?

Please do take this opportunity to give us your input. The team is looking forward to reviewing your suggestions. Oh, and don’t forget to try jQuery 1.7.1 soon!

Read more

jQuery 1.7.1 Released

Here in the United States, we’re celebrating Thanksgiving this week. For those of you living elsewhere in the world, it’s a time when we install and test new versions of Javascript libraries while feasting on Mom’s homemade goodies. Kind of like a code sprint, but with better food. We invite everyone worldwide to join us in these traditions.

To kick off the festivities, the jQuery Team is quite thankful to be releasing version 1.7.1! In this go-round we made Pilgrim’s progress on a cornucopia of bugs, listed below. We are serving up our delicious copies on the jQuery CDN, fresh and warm from the oven:

• http://code.jquery.com/jquery-1.7.1.min.js
• http://code.jquery.com/jquery-1.7.1.js

These latest files should also be up on the major CDNs shortly, but please be patient since this is a holiday week for them as well.

Please install and test this latest slice of jQuery with your code. We hope you’ll find it tasty. If we forgot to fry some turkey of a bug, we want to hear about it. Just put together a specific test case for the problems you’ve found (we love jsFiddle.net for that) and create a bug report at bugs.jquery.com.

Also, please welcome new jQuery Core team member Mike Sherov! We’re thankful to have his help for all the great things we have planned for upcoming versions. Mike has a full-time job at SNAP Interactive in New York City, but contributes to the project in his spare time. Please Be Like Mike and pitch in to help the project any way you can. It doesn’t have to be coding. We can always use help in answering questions on the forum or just reproducing and identifying the source of obscure bugs reported on the bug tracker. See our Getting Involved page for information.

We’ll be opening the call for 1.8 suggestions in just a day or two. Take a look at the 1.7.1 release and think about what kind of awesome sauce we can put on top of it for the next big one!

jQuery 1.7.1 Change Log

The change log of the 1.7.1 release.

Ajax

• #10723: jqXHR.always() returns a Promise instead of a jqXHR object

Attributes

• #10724: $(document).text() always returns an empty string
• #10773: removeAttr is fragile for edge cases

Build

• #10630: Fix focus-related test failures to resolve Swarm failures

Core

• #10616: Type coersion not done for -1 in .eq
• #10646: Have jQuery.error throw instanceof Error object
• #10682: Creating DOM elements with $(‘ ‘) leaks memory and skips the fragment cache
• #10687: jQuery calls the AMD define() global function too early
• #10690: isNumeric

Css

• #10733: remove uses of jQuery.each in css module in favor of a for loop

Data

• #10675: Use internalKey shortcut instead of jQuery.expando

Effects

• #10669: .animate() no longer animates percentage(%) width
• #10750: A “null” in the data object can cause an error in stop

Event

• #10676: wheelDelta not added to mousewheel event anymore
• #10701: Problems with submit forms using submit function
• #10704: special.handle method should fire under origType name
• #10705: off bug event name parser
• #10712: Triggering blur with live bind broken
• #10717: A triggered load bubbles up to window
• #10791: Delegated Events fail on SVG elements
• #10794: .triggerHandler should not .preventDefault()
• #10798: live(“submit”) and .submit() would cause unobtrusive ajax live to fire twice
• #10844: .delegate() on submit doesn’t work when form contains input with name “id”

Manipulation

• #10177: index of callback function in .wrap is always 0
• #10667: HTML5 Support in .wrapAll() does add a “:” to element
• #10670: rnoshimcache probably not constructed correctly
• #10812: passing empty object to .before() or .after() throws exception in IE7

Misc

• #10691: remove all occurrences of the “equals” and “same” function in the unit tests`

Support

• #10629: IE is much too sensitive concerning the fake body. Explore cleaning up support.js to avoid any future crashes.
• #10807: Non-ascii apostrophe in comment

Read more

Getting Board of jQuery

TL;DR The body responsible for overseeing jQuery’s finances and administration, which was until today known as the jQuery Team, is now called the jQuery Board. The jQuery Team is for anyone who invests a significant amount of time contributing to jQuery and its related projects.

As jQuery has grown from a cool idea in 2005 to the most widely used piece of JavaScript on the Internet today, so too has the organizational structure required to support its development and its community. Over time, e-mail chains became mailing lists, and out of those lists evolved a casual confederation known as the jQuery Team. To join this team, all you had to do was make a consistent contribution to some aspect of the project and eventually John would add your name to a page in our docs wiki.

By 2009, the team wanted to solidify the long-term future of the project, so we accepted an invitation to join the Software Freedom Conservancy, from whom we’ve since received great amounts of administrative and legal support. Though the SFC offers that “Projects can continue to operate in the same way they did before joining the Conservancy without having to select a board of directors or any other layer of corporate management,” the team chose to implement a governance system whereby the project’s official decisions would be communicated to the Conservancy after a public vote by the members of the “core team,” which initially had 21 members. This conferred a significant amount of formality onto what had been a relatively ad hoc process, and while the system has worked well, it has been accompanied by some confusion.

• On one hand, there’s the voting membership, responsible primarily for financial and managerial decisions concerning the entire project. On the other, there’s an actual group of people who are working on jQuery Core itself. Both of these groups are sometimes called the jQuery Core Team, which is fairly misleading.
• As new people come along and become active contributors to some part of the project, it’s not fun to tell them, “Hey, great job, but you’re *not* on the team!”
• Just because you are really interested in hacking on jQuery Core, UI, or Mobile (or working on docs, or any of the many other ways you can help out the project) doesn’t mean you have the slightest desire to sit in long meetings, discussing how to allocate funds and how to improve beverage service at the next conference.
• As people’s lives ebb and flow, it’s normal that their capacity to contribute changes. What’s the right correlation between being a genuinely active contributor in the present tense and having a vote in the project’s big-picture management?

In order to attempt to resolve some of this confusion and make clearer the group’s purpose, the jQuery Team is now known as the jQuery Board, and all the governance rules that applied to the Team now apply to the Board. The Board is responsible for

• approving and appropriating expenditures
• representing the intentions of the jQuery Project to the SFC
• overseeing and directing the Subteams and selecting the Subteam Leads responsible for each of the facets of the project
• voting on its own composition

If you’ve always wanted to be “on the team,” but were unsure of what it meant or what you would do, this is good news! We’re fully embracing the Wikipedia definition of team: a group of people (or animals!) linked in a common purpose. As such, anyone who volunteers, over a sustained period of time, to serve actively on a jQuery Subteam will be invited to join the jQuery Team (at the discretion of the Subteam Lead), so you can feel good putting that on your slide decks, refrigerators, and so forth.

What isn’t changing is the fact that if you are passionate about web development and trying to find a way to make a difference to developers around the world, there is a place for you in the jQuery community. Hop onto the forum and give another developer a hand. Head over to our various bug trackers and help triage the open issues — or dive in and see if you can provide a patch. If you just want to get a lay of the land, join the weekly IRC meetings. Want to work on a particular project? Take a look through the updated team page and get in touch with the right subteam lead! One thing’s for sure:

Read more

jQuery 1.7.1 RC1 Released

Just to let you know we’re not asleep at the switch around jQuery Central, we’ve got a new preview release of jQuery. It fixes the problems reported by the community since the original 1.7 release. Please test the code in your applications, making sure that there are no major problems. If you tried jQuery 1.7 and reported a bug, it should be fixed in this release.

You can get the code from the jQuery CDN:

• http://code.jquery.com/jquery-1.7.1rc1.js
• http://code.jquery.com/jquery-1.7.1rc1.min.js

You can help us by dropping that code into your existing application and letting us know that if anything no longer works. Please file a bug and be sure to mention that you’re testing against jQuery 1.7.1 RC1.

We want to encourage everyone from the community to try and get involved in contributing back to jQuery core. We’ve set up a full page of information dedicated towards becoming more involved with the team. The team is here and ready to help you help us!

jQuery 1.7.1 RC1 Change Log

The current change log of the 1.7.1 RC1 release.

Ajax

• #10723: jqXHR.always() returns a Promise instead of a jqXHR object

Attributes

• #10724: $(document).text() always returns an empty string
• #10773: removeAttr is fragile for edge cases

Build

• #10630: Fix focus-related test failures to resolve Swarm failures

Core

• #10616: Type coersion not done for -1 in .eq
• #10646: Have jQuery.error throw instanceof Error object
• #10682: Creating DOM elements with $(‘ ‘) leaks memory and skips the fragment cache
• #10687: jQuery calls the AMD define() global function too early
• #10690: isNumeric

Css

• #10733: remove uses of jQuery.each in css module in favor of a for loop

Data

• #10675: Use internalKey shortcut instead of jQuery.expando

Effects

• #10669: .animate() no longer animates percentage(%) width
• #10750: A “null” in the data object can cause an error in stop

Event

• #10676: wheelDelta not added to mousewheel event anymore
• #10701: Problems with submit forms using submit function
• #10704: special.handle method should fire under origType name
• #10705: off bug event name parser
• #10712: Triggering blur with live bind broken
• #10717: A triggered load bubbles up to window
• #10791: Delegated Events fail on SVG elements
• #10794: .triggerHandler should not .preventDefault()
• #10798: live(“submit”) and .submit() would cause unobtrusive ajax live to fire twice

Manipulation

• #10177: index of callback function in .wrap is always 0
• #10667: HTML5 Support in .wrapAll() does add a “:” to element
• #10670: rnoshimcache probably not constructed correctly
• #10812: passing empty object to .before() or .after() throws exception in IE7

Misc

• #10691: remove all occurrences of the “equals” and “same” function in the unit tests`

Support

• #10629: IE is much too sensitive concerning the fake body. Explore cleaning up support.js to avoid any future crashes



Read more

jQuery Conference 2012: United Kingdom Announced

We are very happy to announce jQuery Conference 2012: UK, the first jQuery conference in the UK, on 10th February 2012. The conference will be held at the Saïd Business School in Oxford with a line-up including six jQuery team members and four industry experts:

Tickets

You can read more about the line-up, talks and location on the event site and tickets are on sale now at EventBrite.

Organizers

The event is being organized by Oxford based digital agency White October with the permission of the jQuery project and with the help and support from jQuery team members. Last year, the jQuery events team tried to put together an event outside the USA and we found how very hard it was to secure a venue from so far away. The jQuery Team is very happy to be working with White October in putting the conference together, and we hope to have you join as we make our European debut!

Sponsorship

If your company is interested in sponsoring the event please take a look at the sponsor pack, please feel free to email or phone (+44(0)207 976 4894) John at White October to discuss the different options.

Read more

jQuery 1.7 RC2 Released

Today, after a very scary Halloween, the jQuery team is releasing jQuery 1.7 RC2 from our Github crypt, er, repo. Barring a report of really terrifying problems or a mob of townspeople at our door with torches, this code will be exactly the same code that becomes the version 1.7 final. If anyone knows of any reason why this code should not become a final release, we need to hear you scream!

In RC2, we fixed a tricky problem that sometimes caused Internet Explorer 8 to go full-zombie when jQuery was loaded. Appropriately enough, the crash was related to creating a detached <body> element that we were using to perform feature detection. IE8 seems frightened to a crashy death when it sees a detached body. If you still see any problems with IE8 crashes, please let us know.

Thanks to a bug report from @warrenparsons, we also fixed a frightful regression with the .show() method. We really appreciate the efforts from those of you who are testing these pre-release versions. Sure, it’s a lot easier to think, “I’ll try it when it’s finally released,” but then any problems you do find will be preventing you — and possibly hundreds or thousands of others — from upgrading. Now that is really scary, at least to us.

During the next day or so we’ll be conjuring up documentation for many of the 1.7 additions and improvements on api.jquery.com. Please bear with us for a few days while we clean up the pages and make sure that it is filled in and all linked properly. For a quick overview of what’s changed, see the 1.7 category.

jQuery 1.7 RC 2 Change Log

The current change log of the 1.7 RC2 release.

Ajax

• #9399: Deprecate jqXHR.success and jqXHR.error

Attributes

• #5479: removeAttr: remove multiple attributes
• #6743: map enctype to encoding, depending on browser
• #10176: Injected script tag is evaluated twice
• #10278: checkboxEl.attr(‘checked’) returns stale value after checkboxEl.click()
• #10429: IE7 – invalid procedure call or argument when calling removeAttr(‘contenteditable’);
• #10514: removeAttr does not remove the class attribute in IE6/7

Core

• #6485: Solution for HTML5 in IE
• #7102: Register jQuery as a CommonjS async module
• #9453: $.inArray does not support fromIndex
• #10478: Switch jQuery.isNaN to jQuery.isNumeric

Css

• #10267: IE8 and window is(‘:visible’) crashes

Data

• #7323: Allow removing multiple data keys at once with $.fn.removeData
• #8909: $(element).data() will scan all attributes more than needed.
• #8921: jQuery private data should stay private

Deferred

• #8856: Request: deferred.isUnresolved()
• #9033: try{ } finally{ } error in IE8
• #9398: Proposal for Improved Deferreds

Dimensions

• #9434: .outerWidth()/.outerHeight()/.innerWidth()/.innerHeight() should work on window and document

Effects

• #5684: Effects: exception in animation callback causes endless loop
• #6150: .stop sometimes doesn’t clear .delay
• #6641: Calling stop() within animation finished callback causes other animations to freeze
• #8685: Animations should keep track of animation state in order to properly address stacked animations
• #9280: Allow multiple effect queues for animate()
• #9548: animate does not work with fill-opacity css property for svg elements
• #10445: Setting queue to true causes an error
• #10497: .stop should allow choosing which queue to stop
• #10622: .show() does not properly restore CSS-set “display” value

Event

• #3368: event.metaKey should be assigned to event.ctrlKey on Non-Mac only
• #6170: jQuery(window).scroll(); causes IE* to scroll to 0,0
• #6319: Regression: stopPropagation inside change handlers in IE is incorrectly applied to keydown event
• #6386: support data argument for live events via “event.special.live.add”
• #6593: IE8: DOM 0 event handler called twice when a separate handler is attached via jQuery
• #6667: submit event doesn’t delegate in IE* under certain conditions
• #6903: special events need a way to determine whether they are being bound with .bind vs .live/.delegate
• #6942: JQuery.event.fix causes unnecessary reflows in IE when handling key events
• #7139: “hover” event alias should work for .bind as well as .live
• #7161: Submit event on a form element not unbound properly in IE
• #7444: Submitting form with “Enter” instead of button click on ie8 or ie7 triggers live submit event twice.
• #8157: Focusing an already focused text field will prevent the change event from firing in IE
• #8728: Event ‘mouseenter’ not firing when the element being left is removed on leaving
• #8789: Meta: Event Property Hooks
• #8858: Special events – _default method doesn’t have access to the `data` argument of the trigger method
• #8866: IE8 input[type=file] delegated change event files only on blur
• #8982: bind(“unload someOther”) => on unload, handler is not executed only once.
• #9069: when hover over a child of an element, mouseleave fires when using live or delegate
• #9279: delegate() bind does not handle mouseover/mouseout and mouseenter/mouseout correctly for selected elements
• #9393: Unify and DRY out event system
• #9593: Delegated submit event is not instanceof jQuery.Event in IE
• #9724: Infinite loop in trigger function when window.parentNode is a DOM element
• #9901: event.handleObj.namespace incorrect when using .delegate
• #9933: jQuery.fn.toggle() should store state in private data object
• #9951: Wrong order in .trigger() when DOM is modified in a handler
• #10375: Do not include `type` in jQuery.event.props
• #10438: Rename jQuery.event.propHooks => .fixHooks
• #10468: Remove deprecated jQuery.event.guid and jQuery.event.proxy
• #10489: Disconnected elements bubble to window on .trigger()
• #10531: Consider removing layerX and layerY from $.event.props
• #10563: jQuery.Event no longer contains the element that matched the selector in event delegation.
• #10567: Delegated events incorrectly match class names
• #10575: Breaking changes in live event propagation between 1.6.4 and 1.7rc1
• #10576: jQuery1.7rc1 and jQueryMobile1.0rc2 – IE gets error in jqm triggerCustomEvent method

Manipulation

• #6782: carefully allow more strings to use innerHTML
• #7037: Duplicate mouseover and mouseout events added to cloned element.
• #10501: HTML5 element “innerShiv” inconsistent across html()/append()

Misc

• #10420: MouseWheel
• #10553: Further reduction of minimal license header

Selector

• #3144: Inconsistent cross-browser results from .text() method
• #5637: Boolean (and Empty) Attribute Selectors Fail
• #6863: faster getText
• #7128: attribute selector is inconsistent between qSA and Sizzle due to use of DOM properties
• #8539: Sizzle cache collision in browsers without querySelectorAll
• #9261: Has Attribute not working in filter/children/siblings
• #9570: Selector $(‘form[name=".."]‘) returns zero elements in IE8 under some conditions
• #10178: $(window).is(“a”) >> Uncaught TypeError: Cannot call method ‘toLowerCase’ of undefined
• #10315: Sizzle ignores seed argument when using positional selectors
• #10562: siblings method returns unexpected elements when using Sizzle-invoking pseudo-selectors

Support

• #5145: jQuery.support.opacity = false in the Chrome browser
• #6809: Add jQuery.support.fixedPosition
• #10558: Test Support bug
• #10613: IE8 doesn’t like a detached body in its head

Traversing

• #10449: Function $(“#id”).closest(“.class”) returns element $(“#id”) itself if it has .class

Read more

jQuery 1.7 RC1 Released

The team is getting closer to jQuery 1.7, and today we’re putting out a release candidate. The full list of fixes and features can be found below. We urge everyone to start testing this code in their applications, so we can make sure that there are no major problems before the final release.

Testing couldn’t be simpler, you can get the code from the jQuery CDN:

• http://code.jquery.com/jquery-1.7rc1.js
• http://code.jquery.com/jquery-1.7rc1.min.js

Please help us by dropping that code into your existing application. If you see something, say something. File a bug and mention that you’re testing against jQuery 1.7 RC1. If there’s a problem we want to fix it.

In the meantime, we’re working on the documentation and release notes to make sure your transition to 1.7 goes smoothly. Stay tuned!

jQuery 1.7 RC 1 Change Log

The current change log of the 1.7 RC 1 release.

Ajax

• #9399: Deprecate jqXHR.success and jqXHR.error

Attributes

• #5479: removeAttr: remove multiple attributes
• #6743: map enctype to encoding, depending on browser
• #10176: Injected script tag is evaluated twice
• #10278: checkboxEl.attr(‘checked’) returns stale value after checkboxEl.click()
• #10429: IE7 – invalid procedure call or argument when calling removeAttr(‘contenteditable’);
• #10514: removeAttr does not remove the class attribute in IE6/7

Core

• #6485: Solution for HTML5 in IE
• #7102: Register jQuery as a CommonjS async module
• #9453: $.inArray does not support fromIndex
• #10478: Switch jQuery.isNaN to jQuery.isNumeric

Css

• #10267: IE8 and window is(‘:visible’) crashes

Data

• #7323: Allow removing multiple data keys at once with $.fn.removeData
• #8909: $(element).data() will scan all attributes more than needed.
• #8921: jQuery private data should stay private

Deferred

• #8856: Request: deferred.isUnresolved()
• #9033: try{ } finally{ } error in IE8
• #9398: Proposal for Improved Deferreds

Dimensions

• #9434: .outerWidth()/.outerHeight()/.innerWidth()/.innerHeight() should work on window and document

Effects

• #5684: Effects: exception in animation callback causes endless loop
• #6150: .stop sometimes doesn’t clear .delay
• #6641: Calling stop() within animation finished callback causes other animations to freeze
• #8685: Animations should keep track of animation state in order to properly address stacked animations
• #9280: Allow multiple effect queues for animate()
• #9548: animate does not work with fill-opacity css property for svg elements
• #10416: defaultDisplay returns block instead of table-row for a tr in FF
• #10445: Setting queue to true causes an error
• #10497: .stop should allow choosing which queue to stop

Event

• #3368: event.metaKey should be assigned to event.ctrlKey on Non-Mac only
• #6170: jQuery(window).scroll(); causes IE* to scroll to 0,0
• #6319: Regression: stopPropagation inside change handlers in IE is incorrectly applied to keydown event
• #6386: support data argument for live events via “event.special.live.add”
• #6593: IE8: DOM 0 event handler called twice when a separate handler is attached via jQuery
• #6667: submit event doesn’t delegate in IE* under certain conditions
• #6903: special events need a way to determine whether they are being bound with .bind vs .live/.delegate
• #6942: JQuery.event.fix causes unnecessary reflows in IE when handling key events
• #7139: “hover” event alias should work for .bind as well as .live
• #7161: Submit event on a form element not unbound properly in IE
• #7444: Submitting form with “Enter” instead of button click on ie8 or ie7 triggers live submit event twice.
• #8157: Focusing an already focused text field will prevent the change event from firing in IE
• #8728: Event ‘mouseenter’ not firing when the element being left is removed on leaving
• #8789: Meta: Event Property Hooks
• #8858: Special events – _default method doesn’t have access to the `data` argument of the trigger method
• #8866: IE8 input[type=file] delegated change event files only on blur
• #8982: bind(“unload someOther”) => on unload, handler is not executed only once.
• #9069: when hover over a child of an element, mouseleave fires when using live or delegate
• #9279: delegate() bind does not handle mouseover/mouseout and mouseenter/mouseout correctly for selected elements
• #9393: Unify and DRY out event system
• #9593: Delegated submit event is not instanceof jQuery.Event in IE
• #9724: Infinite loop in trigger function when window.parentNode is a DOM element
• #9901: event.handleObj.namespace incorrect when using .delegate
• #9933: jQuery.fn.toggle() should store state in private data object
• #9951: Wrong order in .trigger() when DOM is modified in a handler
• #10375: Do not include `type` in jQuery.event.props
• #10438: Rename jQuery.event.propHooks => .fixHooks
• #10468: Remove deprecated jQuery.event.guid and jQuery.event.proxy
• #10489: Disconnected elements bubble to window on .trigger()
• #10531: Consider removing layerX and layerY from $.event.props
• #10563: jQuery.Event no longer contains the element that matched the selector in event delegation.

Manipulation

• #6782: carefully allow more strings to use innerHTML
• #7037: Duplicate mouseover and mouseout events added to cloned element.
• #10501: HTML5 element “innerShiv” inconsistent across html()/append()

Misc

• #10553: Further reduction of minimal license header

Selector

• #3144: Inconsistent cross-browser results from .text() method
• #5637: Boolean (and Empty) Attribute Selectors Fail
• #6863: faster getText
• #7128: attribute selector is inconsistent between qSA and Sizzle due to use of DOM properties
• #8539: Sizzle cache collision in browsers without querySelectorAll
• #9261: Has Attribute not working in filter/children/siblings
• #9570: Selector $(‘form[name=".."]‘) returns zero elements in IE8 under some conditions
• #10178: $(window).is(“a”) >> Uncaught TypeError: Cannot call method ‘toLowerCase’ of undefined
• #10315: Sizzle ignores seed argument when using positional selectors
• #10562: siblings method returns unexpected elements when using Sizzle-invoking pseudo-selectors

Support

• #5145: jQuery.support.opacity = false in the Chrome browser
• #6809: Add jQuery.support.fixedPosition
• #10558: Test Support bug

Traversing

• #10449: Function $(“#id”).closest(“.class”) returns element $(“#id”) itself if it has .class

Read more