You can get the files from the jQuery CDN, or link to them directly: If you can’t yet upgrade to 3.5+, Daniel Ruf has kindly provided patches for previous jQuery versions. Please try out this new release and let us know about any issues you experienced. The jQuery Migrate plugin will help you to identify compatibility issues in your code. If you haven’t yet upgraded to jQuery 3+, first have a look at the 3.0 Upgrade Guide. To upgrade, have a look at the new 3.5 Upgrade Guide. We do not expect compatibility issues when upgrading from a jQuery 3.0+ version. This has now been fixed in jQuery 3.6.3 and it is the only functional change in this release. It should be noted this currently only affects Firefox, but it will be true in all browsers as they roll out changes to CSS.supports. That’s not necessarily a problem in most cases, but it does mean that some level 4 selectors that were supported in browsers but not in Sizzle, like :valid, no longer worked if it was part of a selector list (e.g. This meant that all complex selector lists were passed through Sizzle instead of querySelectorAll. For example: CSS.supports("selector(div)") // trueĬSS.supports("selector(div, span)") // false In CSS.supports( "selector(SELECTOR)"), SELECTOR needed to be a and not a. Apparently, our implementation had a bug. When CSS.supports returned false, jQuery would then fall back to its own selector engine (Sizzle). Using CSS.supports the right wayĪfter the issue with :has that was fixed in jQuery 3.6.2, we started using CSS.supports( "selector(SELECTOR)") to determine whether a selector would be valid if passed directly to querySelectorAll. Here are the highlights for jQuery 3.6.3. Other third party CDNs will probably have it soon as well, but remember that we don’t control their release schedules and they will need some time. More details on that below.Īs usual, the release is available on our cdn and the npm package manager. We wanted to release jQuery 3.6.3 quickly because an issue was reported that revealed a problem with our original fix. There were several changes in that release, but the most important one addressed an issue with some new selectors introduced in most browsers, like :has().
0 Comments
Leave a Reply. |