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에서 preload를 비활성화해야 하는 이유

개발

Gulshan_Kumar (Gulshan Kumar) 12월 31, 2019, 8:05오전 10

6개월 안에 제거되기를 바랍니다.

글		댓글	조회수
Preload certain site images Feature	8	1954	2월 26, 2015
IE 10: Blank page is showing rather not supported message Bug	5	1118	5월 6, 2019
Refused to load preload-store.js Support	6	754	5월 8, 2020
Discourse will be dropping IE9 support in 2016 Feature rfc	14	6941	1월 3, 2016
Odd "data-preloaded" element in HTML Support	1	926	10월 8, 2020

브라우저 업데이트 JS에서 preload를 비활성화해야 하는 이유

Related topics