Second and subsequent fonts not loaded when display=swap is used in webfontloader

When using webfontloader to load web fonts, if display=swap is specified, fonts after the first font are not loaded correctly.

This is because display=swap controls the loading of the webfont and the process blocks the loading of the second and subsequent webfonts. Therefore, if you use webfontloader, you do not need to specify display=swap.

To eliminate the problem of blocked font loading, simply remove the display=swap specification.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top