One of the most useful options in Firefox is the checkbox "Allow pages to choose their own fonts, instead of my selections above"[1], also available as browser.display.use_document_fonts in about:config. When this is unchecked, Firefox will ignore all fonts specified by web pages and just use the much-more-likely-to-be-reasonable choice of default font you have made; and you can then disable web fonts, which will make pages load faster.
I don't think allowing websites to use specific font names in CSS was ever a good idea. It would have been better to limit them to predefined family names, which would map to fonts the user could customize. In any case, this allows me not to care about the whims of website designers and to always have text in a readable font. Only one issue: one of the unfortunate trends in web design is to use web fonts for icons. Not allowing websites to specify different fonts from the default also happens to break the icons. This isn't enough of a big deal for me to disable the option, but it's an annoyance worth knowing about.
Load the page, start reading an article, scrolling as you read. Then the CSS styling kicks in, knocking you back to the top of the page, or worse -- somewhere else entirely, who knows where. So you take some time to figure out where you left off and continue reading again.
But then the font loads. And that shifts everything again. And now you're in the middle of the fourth paragraph when before you were reading the third.
> I don't think allowing websites to use specific font names in CSS was ever a good idea.
I'm with you there. I can't help feeling babied when I visit most websites these days, for more reasons than simply the commonplace (over)use of web fonts.
The problem isnt so much SVG rendering, its that you can grab an icon font with 400 icons that look great, its easy to add them to places beside text, like in menus or on buttons.
You can use SVG, but there is no CDN-hosted SVG sprite with 400 icons to replace things like FontAwesome or Ionicons, so you would have to find all the SVGs you wanted. Then you have the challenge of getting them the right size and position beside text in very tight spaces.
I think the reverse would be a bigger problem: with a limited selection of user-controlled fonts, web designers would use images for fonts, which would be terrible for accessibility and usability.
Viewing it on OS X, it looks like they're using the San Francisco font. A little jarring if you're used to seeing the old typeface 20+ times/day, but it looks good.
The Bold Roboto [1] just looks awful on my machine. Arial [2] looked much better, and if they want to use the system font, Ubuntu [3] also looks much better.
You can alias fonts in Linux, i.e., replace one font with any other. Font Manager is a nice UI for this. I never found anything like it for Windows or OS X.
The idea behind this change seems to be centred around using a modern font no matter what device the user is on while not sacrificing performance. The trade-off here is brand consistency, but if the alternatives are to use an archaic font or a slow webfont, I think this approach wins.
I don't think allowing websites to use specific font names in CSS was ever a good idea. It would have been better to limit them to predefined family names, which would map to fonts the user could customize. In any case, this allows me not to care about the whims of website designers and to always have text in a readable font. Only one issue: one of the unfortunate trends in web design is to use web fonts for icons. Not allowing websites to specify different fonts from the default also happens to break the icons. This isn't enough of a big deal for me to disable the option, but it's an annoyance worth knowing about.
[1]: https://clbin.com/bFSlHF.png