Hi, I noticed Discourse HTML code having below kind of lines <link rel='preload' href='/assets/browser-update-xyz24ff41586d6dcda055f0cfb41488724ba2e2d5271fef65ce5f480b46f9231d.js' as='script'/> <script src='/assets/browser-update-xyz4ff41586d6dcda055f0cfb41488724ba2e2d5271fef65ce5f480b46f9231d…

AFAIK IE is still supported until June, although support is currently being moved into a plug-in.

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

Why would preloading be a problem? I do not understand your request.

[image] Gulshan_Kumar: 6 IE 18 3.17% 7 IE 11 2.99% For rest browsers, it’s not worth wasting users’ bandwidth for unused preloaded resources.

There’s no such thing as IE 18.

It has been ok for the past ~six years. Six months more isn’t a big deal. The reason to spin out IE support is more to reduce complexity than any burden created from preloading.

[image] Gulshan_Kumar: For rest browsers, it’s not worth wasting users’ bandwidth for unused preloaded resources. What about Microsoft Edge?

I hope, in next 6 months it will be removed.

One reason to disable preload for browser-update JS

Development

Gulshan_Kumar (Gulshan Kumar) December 20, 2019, 5:13pm 3

Most of my audience are familier about latest browser. I would be happy to ignore support for IE.

Topic		Replies	Views
Preload certain site images Feature	8	1954	February 26, 2015
IE 10: Blank page is showing rather not supported message Bug	5	1118	May 6, 2019
Refused to load preload-store.js Support	6	754	May 8, 2020
Discourse will be dropping IE9 support in 2016 Feature rfc	14	6939	January 3, 2016
Odd "data-preloaded" element in HTML Support	1	926	October 8, 2020

One reason to disable preload for browser-update JS

Related topics