#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: |
Description
IE11 will no longer be supported by WordPress starting in version 5.8.
The browserslist
array needs to be updated to reflect this.
For context, see:
Change History (11)
#3
follow-up:
↓ 6
@
4 years 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
#4
follow-up:
↓ 5
@
4 years 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
@
4 years 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
@
4 years 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 browserslist
s 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
@
3 years ago
- Keywords needs-docs added
Adding needs-docs
keyword to make sure to udpate the requirements in end-user documentation, if necessary.
In 50784: