link Current Active Support Chrome: (Current - 1) and Current Edge: (Current - 1) and Current [1] , IE mode [2] Firefox: (Current - 1) and Current, ESR [3] Internet Explorer: 11 [2] Safari: (Current - 1) and Current Chrome on Android: (Current - 1) and Current Safari on iOS: (Current - 2), (Current - 1) and Current Any problem with jQuery in the above browsers should be reported as a bug in jQuery. Current denotes that we support the current stable version of the browser, (Current - 1) - that the version that preceded it is supported. For example, if we support (Current - 2), (Current - 1) and Current versions of a particular browser & the current version of a browser is 24.x, we support the 24.x, 23.x and 22.x versions. If you need to support Edge Legacy, Internet Explorer 9-10, iOS 7+ (and not just 3 latest versions) or Android Browser in Android 4.0+, use jQuery 3.x . If, additionally, you need to support Internet Explorer 6-8, Opera 12.1x or Safari 5.1+, use jQuery 1.x .

[1] Only the Chromium-based Edge is supported, Edge Legacy & the old EdgeHTML-based version – is not. [2] We support both the real Internet Explorer 11 and Edge in IE mode, but only in standards mode and in the IE 11 document mode. Read more about IE mode in Edge . [3] Firefox ESR (Extended Support Release) is a Firefox version for use by organizations including schools, universities, businesses and others who need extended support for mass deployments. It is based on a regular release of Firefox and synced from the next regular Firefox every few releases - example ESR versions include Firefox 102, 115 & 128. At any given time there are at most two ESR versions available; jQuery supports all of them. See the Mozilla site for organizations for more information. link Unsupported Browsers While jQuery might run without major issues in older browser versions, we do not actively test jQuery in them and generally do not fix bugs that may appear in them. Similarly, jQuery does not fix bugs in pre-release versions of browsers, such as beta or dev releases. If you find a bug with jQuery in a pre-release of a browser, you should report the bug to the browser vendor. link About Browser Support jQuery is constantly tested with all of its supported browsers via unit tests. However, a web page using jQuery may not work in the same set of browsers if its own code takes advantage of (or falls prey to) browser-specific behaviors. Testing is essential to fully support a browser. Only the most current version of jQuery is tested and updated to fix bugs or add features. Users of older versions that find a bug should upgrade to the latest released version to determine if the bug has already been fixed. The jQuery Migrate plugin may be helpful in identifying and fixing problems during a version upgrade. link About CSS Selector Compatibility Regardless of a browser's support of CSS selectors, all selectors listed at https://api.jquery.com/category/selectors/ will return the correct set of elements when passed as an argument of the jQuery function. CSS styles applied with jQuery's .css() method are dependent on the browser's level of support. In general, jQuery does not attempt to overcome the limitations of a browser's style rendering. (One exception is opacity , which jQuery "shims" for older Internet Explorer's alternative implementation.) Furthermore, prior to version 1.8, jQuery does not normalize vendor-prefixed properties.