I pressed ⌘B. You wouldn’t believe what happened next
summary
A bug where ⌘B bolds Roboto but not Chalkboard leads to concrete engineering choices: Figma picks the nearest numeric weight (often 800) rather than faking strokes, merges OS Google and org shared fonts with tie‑breaking rules, demotes italics in the UI, and synthesizes superscript by measuring metrics and nudging weight. Metadata quality is abysmal (language support ≈ zero), variable fonts break many heuristics, and keyboard legacy (num‑lock, locale shortcuts) forces platform‑specific exceptions — some fixes stick, some surprises remain.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:45The bug
- 6:57Typography
- 9:09Multiplayer
- 15:16Keyboards
- 18:00IBM 5251
- 22:21Windows
- 23:26Keyboard shortcuts
- 27:16Shift 1 Zero
- 29:26Other keyboard shortcuts
- 31:45Unraveling keyboard shortcuts
- 34:06Troubleshooting keyboard shortcuts
- 35:08Solving the mystery
- 36:53The South Church
- 40:49Modifier Keys
- 44:49What do you do
- 45:35Fake Superscript
- 47:44Wrap up
related talks
24mI Pressed ⌘B. You Wouldn't Believe What Happened Next
10mHow we internationalized our typography stack
43mCracking the Code
21mCreate expressive and readable typography with variable fonts
25mTypography is the foundation of any design system
42mTypography for Frontends
13mBest practices for migrating to variable fonts
01h 03mFonts, Form and Function: A Primer on Digital Typography