WordPress.org

Make WordPress Core

Opened 7 months ago

Closed 7 months ago

Last modified 4 months ago

#53077 closed defect (bug) (fixed)

Remove IE11 from the list of supported browsers

Reported by: desrosj Owned by: desrosj
Milestone: 5.8 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: needs-docs needs-codex has-dev-note
Focuses: Cc:

Change History (10)

#1 @desrosj
7 months ago

  • Owner set to desrosj
  • Resolution set to fixed
  • Status changed from new to closed

In 50784:

Build/Test Tools: Remove Internet Explorer 11 from the browserslist.

This officially removes support for Internet Explorer 11 in the CSS files run through the build process in Core.

Individual tickets should be opened for removing each manually maintained area of the code base targeting IE11.

The resulting changes to CSS files are included in this commit.

Fixes #53077.

#2 @desrosj
7 months ago

  • Keywords needs-dev-note added

#3 follow-up: @gziolo
7 months ago

There is also @wordpress/browserslist-config package that @netweb created. Should we align those two configs and make the npm package a source of truth for consistency?

https://github.com/WordPress/gutenberg/blob/trunk/packages/browserslist-config/index.js

Last edited 7 months ago by gziolo (previous) (diff)

#4 follow-up: @netweb
7 months ago

Using and aligning these would be great :)

I just removed IE 11 for the browser support handbook page (And added a changelog note)

https://make.wordpress.org/core/handbook/best-practices/browser-support/

#5 in reply to: ↑ 4 @SergeyBiryukov
7 months ago

Replying to netweb:

I just removed IE 11 for the browser support handbook page (And added a changelog note)

https://make.wordpress.org/core/handbook/best-practices/browser-support/

Thanks! Expanded the changelog a bit to also mention removing support for IE 6 to 10.

#6 in reply to: ↑ 3 @desrosj
7 months ago

Replying to gziolo:

There is also @wordpress/browserslist-config package that @netweb created. Should we align those two configs and make the npm package a source of truth for consistency?

Having a source of truth sounds great. But a disadvantage is that the browser list for Core is now buried in a separate repo on GitHub several folders deep. I am not up to date on best practices for maintaining browserslists for projects, but in my opinion, explicitly including it within the package.json file could potentially make for a better contributor experience, mostly because it's easier to find and more apparent.

#7 @audrasjb
7 months ago

  • Keywords needs-docs added

Adding needs-docs keyword to make sure to udpate the requirements in end-user documentation, if necessary.

#8 @milana_cap
6 months ago

  • Keywords needs-codex added

This ticket was mentioned in Slack in #core by jeffpaul. View the logs.


4 months ago

Note: See TracTickets for help on using tickets.