Prose content in the CP inherits tabular figures
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 62/100
Research direction
Start with the global body rule in the Control Panel stylesheet that sets font-variant to tabular-nums, then find where prose fields (textarea, Bard, Markdown, instructions) inherit it. Reproduce by putting digits like 11 and 111 in a Textarea and in an instruction, and compare with the tabular listings. Done when prose uses proportional figures while tables, listings and the Updates code snippets keep tabular numbers.
Written by the indexing model from the issue text.
Description
Bug description
The CP sets tabular figures globally on body:
body {
font-variant: common-ligatures tabular-nums;
font-feature-settings: "zero", "ss01", "calt" off;
}
That makes sense for dates, listings, tables and similar UI, where numbers should line up. It’s arguably fine for things like <code>11</code> in the “Updates” release notes as well.
But nothing switches back to proportional figures for prose further down, so every text inherits them. That includes the content editors write in Bard, Markdown and Textarea fields, as well as field instructions and descriptions. In running text, narrow digits like 1 take up the width of a 0. Numbers look loosely spaced and uneven.
Text, Bard and Markdown fields handle it a little better. They show the font’s dedicated tabular glyphs, e.g. the 1 with a horizontal foot, which fills the cell and evens out the spacing. Still, tabular figures are the wrong choice for prose.
Textarea fields (and instructions) show it most clearly: the plain 1 sits in a cell as wide as a 0, so 11 (eleven) reads almost like 1 and 1.
Here’s the same text with proportional figures for comparison.
Filenames in the Asset Browser already use proportional figures.
And the tabular figures in listings are correct, too.
How to reproduce
- Add a few fields to a blueprint: Text, Textarea, Bard, Markdown.
- Give them instructions that contain numbers. Narrow digits like 1 show it best, e.g. “Maximum 11 items, 111 characters”.
- Open an entry and type the same numbers into each field.
- Notice the wide, uneven spacing of the digits in the textarea and instructions, and the tabular glyphs in the other fields.
Logs
Environment
Environment
Laravel Version: 12.69.3
PHP Version: 8.4.23
Composer Version: 2.10.2
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: de_CH
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: background
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 4
License Key: Not set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.35.1 PRO
Statamic Addons
daun/statamic-original-filename: 1.1.1
mitydigital/statamic-llms-txt: 1.1.1
statamic/seo-pro: 7.15.1
swiftmade/statamic-clear-assets: 3.4.0
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 118
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statamic/cms
-
fieldtypes ui
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[7.x] Reintroduce parser error for mixed pipe/shorthand modifier syntaxPossibly taken A pull request linked to this issue is open or already merged. Openantlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Read only field dashed border is not visually distinctive enoughPossibly taken @jaygeorge claimed this today. Openui
statamic/cms#15650 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Automattic/blocks-engine#2866 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
community-scripts/ProxmoxVE#17944 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
EasyCorp/EasyAdminBundle#7861 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
backend gamification P0
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
semanadeinformatica/website#461 ·