Problem/Motivation

In #3155358: [policy, no patch] Drop IE11 support from Drupal 10.0.x it was agreed that we no longer need to support IE11 in the Drupal 10 branch. In this issue we will do the work required to remove code that explicitly supports it.

Remove unnecessary polyfills:

Core CSS

Core JavaScript

Subsystem Specific

Comments

longwave created an issue. See original summary.

longwave’s picture

longwave
he/him
Primary language English
Location UK
CreditAttribution: longwave commented
Title: Remove support for IE11 » [meta] Remove support for IE11
Category: Task » Plan

This is likely too big to attempt in one patch, repurposing as a meta.

We need child issues at least for

  • Removing all IE specific CSS, perhaps scoped by theme?
  • Removing conditional comments support from the HtmlTag element
  • Removing the compatibility warnings from CKEditor 5
  • Removing JS polyfills that are only needed in IE
mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented

Yay! I was coming here to create this issue!

Here's a quick braindump:

If I have time later this week, i'll come back and edit the issue summary if anyone hasn't gotten to it yet.

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes

Added a list of polyfills

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes

Adding CSS tasks

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
Issue tags: +CSS, +JavaScript, +IE11

Listing out some subsystems.

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
droplet’s picture

droplet CreditAttribution: droplet commented

IMO, all JS polyfill can be removed together in a single thread. This way you can perform batch SEARCH to find out what LEFT.

AFAIK, it should be a good pattern to SEARCH & REPLACE(REMOVE). If not, we really need to revisit how bad we've done before and improve/avoid it for the next level :)

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
ckrina’s picture

ckrina
she/her
Primary language Catalan
Location Barcelona
CreditAttribution: ckrina at Lullabot commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Priority: Normal » Critical
Issue tags: +Drupal 10, +beta blocker, +pre-alpha target
Parent issue: » #3118149: [meta] Requirements for tagging Drupal 10.0.0-beta1

Just getting this into the right place in the D10 issue tree.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Issue tags: -pre-alpha target

Oops, some of the children can go in before alpha1, but not necessarily all of them.

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes

Updating polyfill issue to #3238501: Remove empty and deprecated IE11 polyfill library stub entries in 11.0.0

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
CreditAttribution: mherchel as a volunteer commented
Issue summary: View changes
gapple’s picture

gapple
he/they
Primary language English
CreditAttribution: gapple as a volunteer commented

I've set these as child issues:
#3101620: Remove IE conditional comments support in Drupal 10
#3214211: Stop setting X-UA-Compatible header

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

Also this? #3256549: Deprecate core/drupal.date asset library in 9.4.0

longwave’s picture

longwave
he/him
Primary language English
Location UK
CreditAttribution: longwave commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Issue tags: -Drupal 10, -beta blocker +Drupal 10 beta blocker
catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch at Third and Grove commented

#3254202: Remove IE11 Support from Claro is close although it could use some help to get it over the line. A couple of Olivero issues still to go too.

The IS mentions settings tray and media, but there are no issues for those, should there be?

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers at Acquia commented
Issue summary: View changes

I think for Settings Tray, the issue was #3291797: Refactor Drupal 10 settings tray / off-canvas to use modern CSS.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch at Third and Grove commented
Issue tags: -Drupal 10 beta blocker +Drupal 10 beta should-have

Changing this to a beta 'should have' since most of these issues aren't actually beta blocking. Anything that is/was beta blocking should already have been surfaced separately.

longwave’s picture

longwave
he/him
Primary language English
Location UK
CreditAttribution: longwave commented
Issue summary: View changes

Opened #3309316: Remove IE11 support from Umami

longwave’s picture

longwave
he/him
Primary language English
Location UK
CreditAttribution: longwave at Full Fat Things commented
Issue summary: View changes

Opened #3309317: Remove normalize-fixes.css

longwave’s picture

longwave
he/him
Primary language English
Location UK
CreditAttribution: longwave at Full Fat Things commented
Issue summary: View changes

Opened #3321006: Drop -ms- vendor prefixed CSS properties

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch at Third and Grove commented
Priority: Critical » Major
Issue tags: -JavaScript +JavaScript

Moving this down to major since it's not really time sensitive, we just need to finish off the child issues, some of which are 11.x only like dependency removals.

Version: 10.0.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.