Drop support for IE 11 and Samsung 4 #23234
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
The title is kind of a farce because we don't actually currently support IE 11 or Samsung 4 because the web components polyfills are not really loaded properly. In any case, this change adjusts the legacy build to stop transpiling and adding core-js polyfills for them.
These 2 browsers are outside our last 7 years support window, and are only included because of the threshold on usage. But since they are considered dead and won't load the frontend anyway, removing them makes sense. It makes extra sense because the minimum versions of the evergreens have recently passed some critical support milestones, so this drops some of the bigger Babel transforms like async functions, classes, template literals, destructuring, and more, and also knocks off about 120 polyfills from Core JS.
Note the minimums also recently passed the milestones for Brotli support, so I can trade Zopfli for Brotli in this PR as well, but please merge #23233 first.
Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: