Dropping support for IE11?

<%- if @topic_view.topic.tags.present? %>
<%= t 'js.tagging.tags' %>: <%- @topic_view.topic.tags.each do |t| %> <%= t %> <%- end %>
<% end %>

Looks like Microsoft will stop supporting IE11 for most of it’s web apps by August 2021.

In the past, we’ve dropped support for browsers when the browser vendor has “end-of-life” it. IE11 is somewhat weird because it shipped with Windows 10 and Microsoft has since adopted a Windows-as-a-service model. Since there’s no Windows 11 on the horizon and Windows 10 will receive updates for the indefinite future, this would in theory mean Microsoft will keep supporting IE11 as well.

Still, if the two-hundred-billion-dollar-multinational doesn’t think it’s worthwhile supporting it’s own legacy browser for its flag ship products, one might wonder why Silverstripe CMS should.

An important note, that this would only apply to the back end part of the Silverstripe CMS. The front end of your site can be targeted to whichever browser you want.

I’m curious, if there’s still much demand for using the CMS with IE11?

Dropping support for IE11 would reduce our maintenance burden and make it easier to develop new UI features. It would also allow us to adopt new JS libraries, although most of the key libraries we use have good IE11 support. A nice side benefit is that would could transpile our JS libraries to ES6 directly and remove a bunch of polyfill which would hopefully reduce the size of our bundles.

I have started dropping IE11 even for front-end support in some sites. For me, I have zero problems telling a client “You need to use a modern browser to use the CMS”. I don’t have government clients, I guess it could be a different story for that sector but I imagine Silverstripe Ltd has good knowledge on that!

A lot of my work is for local government.

A good chunk of them run IE11. The lucky ones are “allowed” Chrome and use that instead. The unlucky ones have to use IE11.

Local government IT teams are incredibly slow moving machines. Are central much better? Thinking CWP…

It’d be great to see some things fixed before “upgrading”. Like in the assets, if I have two windows open and upload a file/image then open assets in the other window, the fresh upload isn’t available until a page refresh. The example also holds in the same window using create buttons. I guess it’s a cache/lazy load problem, understandable in different windows but not so much when in the same window.