New issue
Advanced search Search tips
Starred by 16 users

Issue metadata

Status: Fixed
Closed: Oct 2016
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Launch-OWP
Launch-Accessibility: NotReviewed
Launch-Exp-Leadership: ----
Launch-Leadership: ----
Launch-Legal: NotReviewed
Launch-M-Approved: ----
Launch-M-Target: 56-Dev , 56-Beta , 56-Stable-Exp , 56-Stable
Launch-Privacy: NotReviewed
Launch-Security: NotReviewed
Launch-Test: NotReviewed
Launch-UI: NotReviewed

Blocked on:
issue 680979

issue 554590

Sign in to add a comment

Issue 654679: "system-ui" generic font family

Reported by, Oct 11 2016 Project Member

Issue description

(See for an overview)

Change description:
This generic font family allows authors to style contents so it fits within the system UI.

Changes to API surface:
* Add "system-ui" generic font family.


Support in other browsers:
Internet Explorer: No public signals
Firefox: Shipped “-apple-system” for the compat with WebKit.
Safari: Shipped “-apple-system”, has a bug to alias to “system-ui”.

Comment 1 by, Oct 11 2016

 Issue 555090  has been merged into this issue.

Comment 2 by, Oct 12 2016

Blockedon: 554590

Comment 3 by, Oct 18 2016

Project Member
The following revision refers to this bug:

commit bb3db4f221492076bca16af4d6fb9f358b79cedb
Author: kojii <>
Date: Tue Oct 18 15:30:15 2016

Enable "system-ui" generic font family

This patch enables the "system-ui" generic font family on all

Following changes are planned but not included in this CL:
1. Content sets the current system font to Blink on Linux/CrOS[1].
2. Remove internal use of "BlinkMacSystemFont" and add UMA[2].


BUG= 654679 

Cr-Commit-Position: refs/heads/master@{#425967}


Comment 4 by, Oct 21 2016

Project Member
The following revision refers to this bug:

commit dcc99dfb57774beee88deeb95e8f5753d6d10f8b
Author: kojii <>
Date: Fri Oct 21 07:11:36 2016

Replace internal uses of BlinkMacSystemFont on Mac with system-ui

This patch replaces internal uses of "BlinkMacSystemFont", Blink's
non-standard extension on Mac, with the standard "system-ui" generic
font family.

By eliminating internal uses, the aliasing is moved from FontCache
to CSS resolving time. This allows access to the document, which is
needed for per-document use counter.

BUG=554590,  654679 

Cr-Commit-Position: refs/heads/master@{#426743}


Comment 5 by, Oct 25 2016

Project Member
The following revision refers to this bug:

commit 85fa241e3aa27a6c0c5ecb9c9ca4daa56ea4ac14
Author: kojii <>
Date: Tue Oct 25 03:20:40 2016

Set the font family for the "system-ui" generic font family on Linux

This patch sets the font family for the "system-ui" generic font family
added in [1] on Linux.

With this change, all platforms use the correct font. On Windows, the
browser already pass menu_font_family_name to the renderer. On Mac and
Android, the render can find the system font without needing the
browser to set.

On Linux and Chrome OS, gfx::Font() calls LinuxFontDelegate to figure
out the current system font. On the default Ubuntu, this resolves to
"sans", which Skia resolves to "DejaVu Sans", or "Arial" in


BUG= 654679 

Cr-Commit-Position: refs/heads/master@{#427262}


Comment 6 by, Oct 26 2016

Blockedon: -554590
Blocking: 554590
Status: Fixed (was: Assigned)
Supporting OS-defined cascading list on Mac is still left, but since the old BlinkMacSystemFont doesn't support it either, we can improve it in future releases.

All other work are done, marking as fixed.

Comment 7 by, Dec 14 2016

Is there any testing needed from TE? If yes please respond to test survey.

Comment 8 by, Jan 9 2017

Is there any manual testing needed from Android TE? If so can you please fill out the survey as per #7 ?

Comment 9 by, Jan 18 2017

Blockedon: 680979
Sorry I missed #7.

1. Feature implementation status (what is currently working and not working/known issues, ready for testing etc.)

The feature is implemented and is ready for testing.
Known issues: issue 680979

2. Link to Design Doc:

3. Link to Test Plan: ( High level testcases,specific setup,flags etc)


4. Link to demos (if any):


5. Targeted Platforms.


6. What's automated? (Unit tests, API tests, Browser tests)  Please provide links to automated tests.

7. Does the feature needs manual testing?

The automated test covers the basic cases.

8. Are there any special points of interest from a testing perspective?

This feature retrieves the system font family name from the system, and how to do it depends on the platform.

Most OS provides an API and Blink relies on it. Android and Linux don't, so Blink relies on heuristics. There are some tools that changes system fonts on Android, such as the one built into Samsung devices, but the behavior is not guaranteed due to the lack of the official API in Android.

9. Is there a mechanism to turn off the feature if it breaks product functionality or performance?


10. List UMA stats and coverage to measure stability. It’s highly recommend always adding Stability.Counts and CrashExitCodes.* to your json.


11. Any performance impact? Did the feature get tested on perf waterfall?

No perf waterfall, the perf impact is highly unlikely. The feature kicks in only when author uses "system-ui" in the font family, and caches the result in the renderer.

12. What is the crbug label for the feature?


13. Are there any other team members or mailing lists that should be notified if issues are found?

drott@, eae@,

Comment 10 by, Jan 26 2017

Chrome on Android TE wrapped up "system-ui" generic font family testing on M56 (56.0.2924.78) 

Devices covered
Sony Xperia C/4.2.2 (arm) 
Samsung Galaxy  Core2(SM-G355M) / KOT49H
Predator  / LMY47I (X86_64)
S6 (SM-G920F) / MMB29K 
Pixel XL/ NMF26U (arm_64)

Blockers issue 680979 and issue 685285 are fixed.

Comment 11 by, Nov 22 2017

From,  I'm afraid Chrome does not pick "UI" fonts (as opposed to 'body/document' fonts ) on Android and Chrome OS when 'system-ui' generic family is specified.  (haven't tested yet). 

Android's fonts.xml has two fallback branches for sans-serif. One is 'elegant' and the other is 'compact'. When there is a distinction between UI fonts and 'body/document' fonts, elegant is for the latter and compact is for the former. 

For LGC, Roboto is for both, but for a lot of other scripts (e.g. South Asian and SE Asian, Arabic scripts), the distinction matters. "Noto Sans <script name>' is for document/body and 'Noto Sans <script> UI' is for UI. 

When 'system-ui' generic family is specified, 'Noto Sans <script name> UI' has to be picked instead of 'Noto Sans <script name>'. Is it the case now? 

Windows also has separate UI fonts. Segoe UI is well known, but does not cover every script. Nirmala UI is for Indic script, Meiryo UI for Japanese, Microsoft {Jheng,Ya}Hei UI for Chinese, etc. Perhaps, on Windows we pick these fonts by default. 

On Chrome OS (with Noto Sans <script> and Noto Sans <script> UI fonts), there are two ways:

1) add a new font preference for 'system-ui' per script (as is the case for 'sanserif' and 'serif' per script font preference)

2) add a support for a new generic family to fontconfig and refer to it. 
(I'm raising an issue in fontconfig ml - I've seen a thread on this topic before, but I couldnt' find it). 

The 2nd method can be used on Linux, too. I think we need to do both. 

#1 is useful when a user wants to have a fine control over what's used for 'system-ui' generic family via Settings (instead of relying on the default values). 

I'll file follow up bugs.

Sign in to add a comment