# One reason to disable preload for browser-update JS

**URL:** https://meta.discourse.org/t/one-reason-to-disable-preload-for-browser-update-js/136693
**Category:** Development
**Created:** [December 20, 2019, 4:48pm UTC](https://meta.discourse.org/t/one-reason-to-disable-preload-for-browser-update-js/136693 "2019-12-20T16:48:21Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [December 20, 2019, 5:20pm UTC](https://meta.discourse.org/t/one-reason-to-disable-preload-for-browser-update-js/136693/4 "2019-12-20T17:20:06Z")

</div>

### Move Internet Explorer support to core plugin

Discourse will be dropping support for Internet Explorer in June 2020. (A formal announcement will be made mid-January). In preparation for this, Internet Explorer specific code has been moved into a plugin, making it easier to remove come June.

[Source](https://meta.discourse.org/t/discourse-2-4-0-beta9-release-notes/136517)

---

_[View the full topic](https://meta.discourse.org/t/one-reason-to-disable-preload-for-browser-update-js/136693)._