At the end of last year, a bug occurred in Chrome browser, at least on Mac systems (the situation on other platforms is unknown), the system fonts are too thin under small sizes, and the word spacing is too tight; in large sizes, it looks too thick and the word spacing is too wide. Fortunately, the issue has been fixed. However, during the period when the problem existed, I gave up the system font and switched to other fonts. Although the performance dropped slightly, the visual effect improved.
Now a more serious problem occurs: the system font cannot be bolded. This is very bad because many websites use a system font stack because it has two major advantages: 1) helps the website to look consistent with the operating system; 2) has excellent performance because the website does not need to download and display custom fonts.
Jon Henshaw reported on this:
...This bug caught the attention of Adam Argyle, the developer of VisBug and the evangelist of Google's Chrome CSS developer. Argyle created a Chromium bug report, but the Chromium development team finally decided that this would not hinder the release of version 81. This causes sites like Coywolf to fail to use bold text for fonts larger than 16px (e.g., per title).
Since the Chromium team announced the skip of version 82 and will release version 83 in mid-May, the bug will not be fixed in version 82. Argyle assured everyone in the initial GitHub bug report that it will be fixed in version 83.
So we have to wait about four more weeks. ?ime Vidas recommends using Helvetica fonts temporarily as a temporary solution:
<code>body { font-family: -apple-system, Helvetica; }</code>
I think older versions of Chrome/macOS may still benefit from system fonts due to the inclusion of -apple-system
? I'm not sure.
This made me a little confused. When I first heard about using a system font stack, there are -apple-system
and BlinkMacSystemFont
and you should use them in the font stack in this order. Then there comes -system-ui
, which seems to work well alone, which is great because it obviously doesn't rely too much on the Mac system. But there is also system-ui
(without starting dash), which seems to do the same thing, I'm not sure which is correct. Now it seems that the plan is ui-sans-serif
and its related fonts (such as ui-serif
and ui-monospace
). I like the idea, but I hope to get clear instructions from browser vendors about recommended usage. Are we in this situation?
<code>/* 只是一個(gè)猜測(cè)... */ body { font-family: ui-sans-serif, system-ui, -system-ui, -apple-system, BlinkMacSystemFont, Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji"; }</code>
Another observation of mine is... When I try to copy this bug on Chrome 81, at first I thought "strangely, it works fine on my system" because I'm trying to bold the default 16px text. I noticed that when the font size is 20px or larger, the problem arises:
Bramus proposes another solution: use Inter fonts.
The above is the detailed content of Chrome System Fonts Snafu. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

CSSselectorsandpropertynamesarecase-insensitive,whilevaluescanbecase-sensitivedependingoncontext.1)Selectorslike'div'and'DIV'areequivalent.2)Propertiessuchas'background-color'and'BACKGROUND-COLOR'aretreatedthesame.3)Valueslikecolornamesarecase-insens
