Prose content in the CP inherits tabular figures
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- Medio día
- Aptitud para principiantes
- 62/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- PHP
- Estrellas
- 4.9k
- Forks
- 647
- Merge medio
- 1 d 17 h
- PR fusionados (30 d)
- 111
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de statamic/cms
-
CP sidebar checks every site for each navigationPosiblemente ocupada @lazerg la tomó hoy. Abiertomultisite performance
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Make native filesystem directory permissions configurable to support shared POSIX ACL accessAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
accessibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
antlers
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
caching nocache
Dificultad 3/5 1-2 días Aptitud para principiantes 42/100
statamic/cms#15643 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de statamic/cms
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
nextcloud/integration_openai#446 ·
-
bug customer-reported
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
MagnaCapax/PMSS#1101 ·
Los mantenedores suelen responder en 5 días
-
InvoiceSettled is answered 200 when the invoice cannot be re-fetched, so BTCPay never redelivers itAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
btcpayserver/woocommerce-greenfield-plugin#93 ·
Los mantenedores suelen responder en 1 día
-
kind/bug status/triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100