Core: Drop support for IE (all versions) #5077
Conversation
| // Support: IE 11+ | ||
| // ...but not arrow key "clicks" of radio inputs, which can have `button` -1 (gh-2343) |
There was a problem hiding this comment.
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.
test/delegatetest.html
Outdated
| } else if ( 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); |
There was a problem hiding this comment.
This file has been broken for a long time due to the use of live… But it looks potentially useful so I fixed it.
|
Seems like the right move at this point. Things clean up nicely! |
8e858d1 to
54f3294
Compare
|
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" |
|
@ollie-iterators Thanks for the info; that should say 5.0; we’ll fix it. |
65f8165 to
469a9b2
Compare
|
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. |
|
@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. |
173239b to
b3e684a
Compare
|
IE drop 4.1.0 ? |
|
@nagyimre1980 No; we treat reducing browser support policy as a breaking change so it has to land in a major version update. |
36ed210 to
a35b89d
Compare
21d7938 to
088ce96
Compare
b74888f to
a76a48b
Compare
356bdd0 to
5222e6a
Compare
630c5cb to
6660f03
Compare
6660f03 to
4768ef2
Compare
7bd57c0 to
ebcbd3b
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
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. |
|
By removing IE support, you also remove many crutches and difficult logic that aren't needed in the modern browsers. |
|
Furthermore, please check this — IE isn't used at all. |
|
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 to extend support for ESR 115 only on Windows 7-8.1 and macOS 10.12-10.14 up to March 2026. |
|
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) |
Summary
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:
Checklist
New tests have been added to show the fix or feature worksIf needed, a docs issue/PR was created at https://github.com/jquery/api.jquery.com