~~This PR is to show what dropping IE support would look like in code. If we make a decision to drop IE in v4, this PR can be merged, guarded on possible review remarks.~~ EDIT: we've decided to land this in5.0.0.

Of course, dropping IE would open a lot of other doors for various refactors but those would be considered separately.

Size difference:

main @65e35450c9954173dc1ddd3576242a913d8efb88   raw     gz     br Filename -1926   -608   -517 dist/jquery.min.js -1720   -550   -556 dist/jquery.slim.min.js -1926   -611   -609 dist-module/jquery.module.min.js -1720   -555   -522 dist-module/jquery.slim.module.min.js

Checklist

~~New tests have been added to show the fix or feature works~~
~~If needed, a docs issue/PR was created athttps://github.com/jquery/api.jquery.com~~

mgol requested review fromdmethvin,gibson042 andtimmywil

July 26, 2022 23:09

mgol commented

Jul 26, 2022

View reviewed changes

src/event.jsShow resolvedHide resolved

mgol commented

Jul 26, 2022

View reviewed changes

src/event.js

Comment on lines -366 to -357

		// Support: IE 11+
		// ...but not arrow key "clicks" of radio inputs, which can have `button` -1 (gh-2343)

Copy link

MemberAuthor

mgolJul 26, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Firefox doesn't have the behavior from the above comment (click events are not fired for non-primary mouse buttons) so perhaps this all could be removed. But one of our tests checks this condition explicitly so I'd rather leave it for a separate PR.

mgol commented

Jul 26, 2022

View reviewed changes

src/selector.jsShow resolvedHide resolved

mgol commented

Jul 26, 2022

View reviewed changes

test/delegatetest.html Outdated

		}elseif(api==="bind"){
		$(this).find("input, button, select, textarea").on(type,$cell,blinker);
		}else{
		$(id+" input,"+id+" button,"+id+" select,"+id+" textarea").live(type,$cell,blinker);

Copy link

MemberAuthor

mgolJul 26, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This file has been broken for a long time due to the use oflive… But it looks potentially useful so I fixed it.

mgol added Needs review Discuss in Meeting

Reserved for Issues and PRs that anyone would like to discuss in the weekly meeting.

Core labels

Jul 27, 2022

mgol self-assigned this

Jul 29, 2022

Copy link

Member

dmethvin commentedAug 2, 2022

Seems like the right move at this point. Things clean up nicely!

mgol added this to the5.0.0 milestone

Aug 8, 2022

mgol removed the Discuss in MeetingReserved for Issues and PRs that anyone would like to discuss in the weekly meeting. label

Aug 8, 2022

mgol removed the Needs review label

Jan 20, 2023

mgol force-pushed thedrop-ie-support branch from38a8406 to9aeffcbCompare

March 14, 2023 12:10

mgol force-pushed thedrop-ie-support branch 2 times, most recently from8e858d1 to54f3294Compare

April 6, 2023 10:30

Copy link

ollie-iterators commentedMay 12, 2023

The blog about jquery 3.7.0:https://blog.jquery.com/2023/05/11/jquery-3-7-0-released-staying-in-order/ says that "support for IE will be dropped in jQuery 4.0"

Copy link

MemberAuthor

mgol commentedMay 12, 2023

@ollie-iterators Thanks for the info; that should say 5.0; we’ll fix it.

azu mentioned this pull request

May 19, 2023

2023-05-19のJS: jQuery 3.7.0、Vue 3.3、Bun 0.6.0(bun build)jser/jser.github.io#1081

Merged

mgol force-pushed thedrop-ie-support branch 2 times, most recently from65f8165 to469a9b2Compare

July 10, 2023 21:42

Copy link

vrubleg commentedAug 27, 2023

It's 2023, IE11 is 10 years old, half of the web already doesn't work in this browser. IE11 was introduced with Windows 8.1 that is already not supported by a lot of software (including Firefox and Chrome) and libraries (like Qt6+ or Python 3.9+). It makes sense to drop IE earlier.

Copy link

MemberAuthor

mgol commentedSep 6, 2023

@vrubleg I understand the sentiment and I admit more than a year has passes since I raised this PR but I really don't want to make any changes to our 4.0.0 plans at this point as any further change is just going to delay the whole thing, and it's already been delayed a lot.

I want to get the beta out with only our current blockers resolved. Once we have that, once we also have the respective Migrate release and the upgrade guide prepared, we can talk about it once again.

mgol force-pushed thedrop-ie-support branch 3 times, most recently from173239b tob3e684aCompare

September 20, 2023 20:25

Copy link

nagyimre1980 commentedSep 21, 2023

IE drop 4.1.0 ?

Copy link

MemberAuthor

mgol commentedSep 21, 2023

@nagyimre1980 No; we treat reducing browser support policy as a breaking change so it has to land in a major version update.

mgol force-pushed thedrop-ie-support branch 2 times, most recently from36ed210 toa35b89dCompare

September 21, 2023 23:45

mgol force-pushed thedrop-ie-support branch 3 times, most recently from21d7938 to088ce96Compare

November 20, 2023 13:40

mgol force-pushed thedrop-ie-support branch 2 times, most recently fromb74888f toa76a48bCompare

March 20, 2024 00:28

mgol force-pushed thedrop-ie-support branch 2 times, most recently from356bdd0 to5222e6aCompare

May 10, 2024 21:05

mgol force-pushed thedrop-ie-support branch 2 times, most recently from630c5cb to6660f03Compare

September 16, 2024 21:23

mgol force-pushed thedrop-ie-support branch from6660f03 to4768ef2Compare

November 25, 2024 23:05

mgol force-pushed thedrop-ie-support branch 3 times, most recently from7bd57c0 toebcbd3bCompare

January 30, 2025 09:43

mgol force-pushed thedrop-ie-support branch fromebcbd3b to7c9d1ddCompare

March 3, 2025 22:35

mgol removed the request for review fromdmethvin

March 3, 2025 22:36

mgol force-pushed thedrop-ie-support branch from7c9d1dd to01d86a8Compare

April 2, 2025 12:00

This comment was marked as off-topic.

Copy link

IRainman commentedSep 26, 2025

Why only in 5.0? WebView on Windows 7 is much more functional and convenient and also too outdated as IE11… IE11 isn't legacy; it's dead completely. You can use many improvements in code generation with let and const as basic features, and many more if we drop support for IE completely.

Copy link

IRainman commentedSep 26, 2025

By removing IE support, you also remove many crutches and difficult logic that aren't needed in the modern browsers.

Copy link

IRainman commentedSep 26, 2025

Furthermore, please checkthis — IE isn't used at all.

Copy link

IRainman commentedSep 26, 2025•
edited
Loading

Moreover,Firefox ESR 115 still supports Windows 7 and plans to support it until 2026. You can completely remove support for IE without any issues.

We decided toextend support for ESR 115 only on Windows 7-8.1 and macOS 10.12-10.14 up to March 2026.
We will re-evaluate this decision in February 2026 and announce any updates on ESR 115's end-of-life then.

Copy link

nagyimre1980 commentedSep 26, 2025•
edited
Loading

Agree. IE11 has been dead for years! Considering the current release pace, in my opinion, 5.0 will take at least 4-5 years to appear!My main issue: Speed: It would be noticeably faster if we removed all those IE11 branches!The final release of 4.0 is still many months away (I don't think it'll even come out this year)