Make WordPress Core

Opened 3 days ago

Last modified 20 hours ago

#49696 new task (blessed)

Define guidelines for minimum IE support

Reported by: isabel_brison Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: accessibility, javascript, css Cc:


IE usage is decreasing steeply, but is still just enough that we have to support it. One concern is that there is a disproportionate amount of screen reader users that still depend on it, as confirmed by the latest WebAIM survey: https://webaim.org/projects/screenreadersurvey8/#browsers

With this in mind, it would be good to set guidelines for the level of support required for IE, so as to allow us to safely make use of newer technologies while guaranteeing accessibility for IE users.

  • If we allow the experience to degrade gracefully, what is the essential functionality that must be preserved?
  • What level of testing should be required to make sure everything works on IE?

Change History (12)

#1 @afercia
3 days ago

  • Focuses accessibility added

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

3 days ago

#4 @azaozz
41 hours ago

  • Focuses javascript css added
  • Milestone changed from Awaiting Review to Future Release
  • Type changed from feature request to task (blessed)

Thanks @isabel_brison, great idea to track the progress on this. Changing the ticket type to "task" as it is not milestone related.

For starters, here's some current info about IE11 as of March 2020:

  • Total usage: 1.63% (statcounter.com) - 2.39% (netmarketshare.com).
  • Lifecycle: as IE11 is part of Windows 10, the EOL is the same for both. The latest release of Windows 10, version 1909, will be supported until May 11, 2021 for for Home, Pro, Pro Education, and Pro for Workstations, and May 10, 2022 for for Enterprise and Education editions (support.microsoft.com).
Last edited 41 hours ago by azaozz (previous) (diff)

This ticket was mentioned in Slack in #core-css by isabelbrison. View the logs.

40 hours ago

#6 @netweb
33 hours ago

Related: #48743 Consider adding a notice do discourage IE11 usage

#7 @twocs
33 hours ago

I don't like supporting IE11 but rumours of its impending demise may be exaggerated.

Internet Explorer 11 is the last major version of Internet Explorer. Internet Explorer 11 will continue receiving security updates and technical support for the lifecycle of the version of Windows on which it is installed. https://support.microsoft.com/en-au/help/17454/lifecycle-faq-internet-explorer-and-edge

Microsoft will continue to support at least one Windows 10 Semi-Annual Channel until the extended support date of October 14, 2025. https://support.microsoft.com/en-au/lifecycle/search/18165

My interpretation is that this means that Windows 10 could be supported beyond 2025, and IE11 by extension. Some long term enterprise versions of Windows 10 are supported until 2029.

Last edited 33 hours ago by twocs (previous) (diff)

#8 @slkfsdf8y34ljhsfsdfkuhfkl84hj
28 hours ago

Comments use passive listeners and degrades the performance on sites with large amount of comments.

That's one of the reasons why the Google's Lighthouse scores are low on sites with WordPress installed.

The situation is solved only after running a special type of CDN that loads the content in a special way.

You should ditch the support for IE11 and improve the performance.

With the new features that new browsers, OSes and devices introduce for accessibility reasons, IE11 for sure is actually a worse option for them.

Btw I am not sure if the 3.39% shown for IE usage by W3 Counter is real as it may count the IE mode on Edge as IE11. Typically this mode is used by institutions to browse special sites or internal resources.

However with the discovered vulnerabilities and things, MIcrosoft is pushing updates and governments would buy new licenses and upgrade very fast.

Also Microsoft granted free upgrades extensions.

A lot of state websites were vulnerable and they would be fastly refactored so the IE mode won't be used as much on Edge.

That means that fake usage percentage would drop considerably.

Reported IE11 usage is not real, it is based on large scale due to the IE mode on Edge for administrative and government purposes.

Low-income and first-Internet access in the Third world now happens primarily with mobile phones, these phones primarily uses Chromium based browsers and Firefox, not IE11.

So the idea for discriminating someone with low income is not true in that sense. IE11 users are not Third world users.

I don't think the percentage is enough for you to support IE11.

The sites may still be browsable to some level, but you shouldn't anymore support IE11.

Even big corporations like Microsoft cut support on things like the Windows 7 despite the large amount of users and incentivizes them to move on with some tricks like the newly introduced "bugs".

Stop using passive listeners so that mobile users could benefit from an improved performance.

We need to "push" things in some sense as otherwise we would always be stuck in progress.

Apple ditched 32-bit support for applications despite many people using apps that would probably never be updated. That happened both on their mobile and desktop platforms.

There is some sort of "courage" needed to push things forward.

The real base of IE11 which is not properly represented in the statistics is far smaller and you shouldn't take it into account.

Last edited 28 hours ago by slkfsdf8y34ljhsfsdfkuhfkl84hj (previous) (diff)

#9 @burtrw
22 hours ago

To help maybe quantify the number of people that may be using IE11 beyond the general stats mentioned above, here are the percentages of browsers used by visitors to edublogs.org in the month of February 2020. Edublogs gets global traffic, with a large percentage of those in schools around the world (which are notorious for having outdated hardware and require the use of IE).

Top 10 Browsers

IE Versions

I also note that IE use is only slightly down from 2.13% of all visitors to Edublogs in February 2019 to 2.01% of visitors in February 2020. Before digging into this, I expected the drop in usage to be greater than it actually was.

It might be useful to see similar browser usage from other larger WordPress sites? To me, 2% is not really that insignificant, unfortunately. That being said, the idea of being able to safely make use of newer technologies while still not breaking or making sites on IE usable seems reasonable, if it is technically possible.

#10 @Ipstenu
21 hours ago

A concern about this is not just the volume of users but who they are.

The people stuck on IE are often in government or financial sectors and are prohibited by law from upgrading things. The people who use IE 11 aren't just your parents who won't upgrade a laptop, they're people who actually have no agency over this change.

Keep in mind that any change we make that makes WP unusable for them will have larger consequences.

Yes, it sucks a LOT, but having worked in financial for 14+ years before I ran away, they're simply not capable of upgrading, and will stay using out of date and insecure products because they have no choice. Whatever we do, we have to keep them in mind.

#11 @slkfsdf8y34ljhsfsdfkuhfkl84hj
20 hours ago

People who work for the governments around the world or financial institutions are required by law to upgrade after the extended support ended, unless these institutions pay an astronomical fee which makes it only valuable for super extreme cases like some ancient military facilities.

A large portion of the counted as IE11 users are actually Edge users that are using the "IE mode" on it.

Microsoft and Apple did some nasty tricks in order to force obsolescence. I think counting the performance enhancement that WordPress would gain by stopping using passive listeners would be significantly bigger value than keeping IE11 support.

Even Facebook doesn't support IE11 anymore and we both know what kind of users are using it.

#12 @Ipstenu
20 hours ago

People who work for the governments around the world or financial institutions are required by law to upgrade after the extended support ended, unless these institutions pay an astronomical fee which makes it only valuable for super extreme cases like some ancient military facilities.

This is weirdly not true for all nations. Heck, not even true for all states in the US. Keep in mind, EOL is *2022* -- while that's two years away, it's also possible that there will be extensions like there were for Windows 8.

In some cases, they are required by law to use hardware or software written by one and only one check processing vendor on the planet, who refuses to update. I wish I was pulling that example out of thin air.

(Facebook not supporting IE doesn't really count here, since that's ONLY for social networking and unlikely to be open source product a company uses daily -- in fact, I'd bet most companies wold be totes okay that Facebook's broken)

My point remains this: We need to be very thoughtful and careful about what we break and how we handle workarounds. It would not be a bad idea to have an 'IE Compatibility Pack' type plugin to restore old functionality for these people in terrible situations. We just need to make sure we give them agency to move forward that isn't just "Lulz sucks! get a new browser!"

Note: See TracTickets for help on using tickets.