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.

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

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.

[изображение] 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.

[изображение] 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.

Одна из причин отключить предварительную загрузку для JS browser-update

Разработка

Justin_Vega (Justin Vega) 30.Декабрь.2019 20:32:45 9

А что насчёт Microsoft Edge?

Тема		Ответов	Просм.
Preload certain site images Feature	8	1954	26.02.2015
IE 10: Blank page is showing rather not supported message Bug	5	1118	06.05.2019
Refused to load preload-store.js Support	6	756	08.05.2020
Discourse will be dropping IE9 support in 2016 Feature rfc	14	6941	03.01.2016
Odd "data-preloaded" element in HTML Support	1	926	08.10.2020

Одна из причин отключить предварительную загрузку для JS browser-update

Связанные темы