Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Prose content in the CP inherits tabular figures

Aperta
  • Qualcosa non va?
#15,658 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
62/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
css, laravel, php
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Image
Here’s the same text with proportional figures for comparison.
Image
Filenames in the Asset Browser already use proportional figures.

And the tabular figures in listings are correct, too.

Image
How to reproduce
  1. Add a few fields to a blueprint: Text, Textarea, Bard, Markdown.
  2. Give them instructions that contain numbers. Narrow digits like 1 show it best, e.g. “Maximum 11 items, 111 characters”.
  3. Open an entry and type the same numbers into each field.
  4. 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

Lingua principale
PHP
Stelle
4.9k
Fork
647
Merge medio
1g 18h
PR unite (30g)
118

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di statamic/cms

Tutte le issue di statamic/cms

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.