End date for IE11 Support for front-end javascript

[davejtoews]

With Silverstripe 4.10 being released the CMS is dropping IE11 support. This should only impact sites that need CMS editing done in IE11, so in theory one can still build a public facing front end that supports IE11. However this module includes javascript that is run on public facing pages with userforms. Is there an intention to drop IE11 support here?

It does not appear that the latest release includes significant changes for the JS, but it would be helpful to know if and when we should stop upgrading this module for any sites using it that still support IE11.

[emteknetnz]

@maxime-rainville

[maxime-rainville]

That's a good point. We didn't go out of our way to break anything in this release, so I expect the CMS and related modules will still be usable in IE11. We don't have any short term plans that will require us to break things for IE11.

But at some stage, the same logic that got us to drop support for IE11 in the CMS will apply here as well ... MS is no longer supporting IE11 and is actively dropping support for it across its own web application. I'm disinclined to put any energy into actively testing this module in IE11 or putting effort into fixing IE11 bugs.

If some projects absolutely need IE11 support, I would be tempted to put it back on them to do their own testing before upgrading. If they find IE11 bugs and want to fix them, I would be fine merging those fixes in.