![]() After fonts have loaded on the rightĪs the speed of internet connections improved, less focus was placed upon optimising the amount of information transferred, and whilst that was shortsighted, it simply reflected the attitude of the time. Over the years, due to poor user experiences (caused by slow load times, or sometimes not loading at all), font loading strategies were developed to address symptoms, like Flash of Unstyled Text, and its various incarnations.īefore fonts have loaded on the left. The problem, though, was fonts could be quite large assets, some being several hundred kilobytes (this is still true today). ![]() Whilst the benefits of custom fonts are evident to most, what wasn’t evident, measured, nor understood (for quite some time), were the impacts to UX, performance, and the environment. From matching a brand’s font, to flourishes designed to entice and create interest, the options were endless. Widespread support for custom fonts brought creative options that were simply not possible before in web development. Whilst Internet Explorer 4 was the first browser to adopt custom fonts, it would be a long wait until 2011 where support for custom fonts was supported across the big four browsers Internet Explorer, Chrome, Safari and Firefox. The problem? A lack of industry standardisation resulted in near zero support from other browsers. ![]() Along with it, the first means for downloading custom fonts in a browser. The year is 1997 and Microsoft releases Internet Explorer 4. Couple that with limited crossover of font options between the operating systems, and most of the time, this resulted in all websites using four fonts: Arial, Helvetica, Verdana, and Times New Roman. In the early days of web development (circa 1997), web design was limited to fonts that were available with the operating system, be that Windows, MacOS, or Linux.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |