Real-world impact of the tabular "1" foot (#557/#579) — asking for a timeline on cv15 / v4.2
Author: Faizuddin-qCreated Sep 17, 2026Updated Sep 17, 2026
## What's happening
When `font-variant-numeric: tabular-nums` is turned on, Inter's "1" gets a small foot/serif at the bottom instead of a plain vertical stroke. In a normal paragraph this is barely noticeable, but in a live-updating numeric dashboard (prices, margins, balances) it stands out a lot — the "1" almost looks underlined, and it's easy to misread at a glance next to a column of other digits.
I saw this is already tracked in #557 (original report) and #579 (request for a way to turn the foot off), and that the fix is merged in commit `a264bbe`, planned for v4.2 as character variant `cv15`. I'm opening this to add a real-world example and ask about timing, since v4.1 has been out since November 2024 with no v4.2 yet.
## Minimal reproduction (copy-paste into any HTML file)
Proportional (default): 1,234.56
Tabular (tnum): 1,234.56
Open this in a browser — compare the "1" in the first line (plain stroke) vs. the second line (footed/underlined look). ## Why it matters to us We use Inter with `tabular-nums` across a live trading dashboard where numbers update in real time (margins, P&L, deposits). Screenshot attached below shows the effect in a real UI, not just an isolated character. ## Related issues already reported by others - Bottom stroke for tabular /one — https://github.com/rsms/inter/issues/557 - Request: tabular `1` without bottom slab — https://github.com/rsms/inter/issues/579 - Additional monospaced characters when using tabular figures — https://github.com/rsms/inter/issues/227 - Make tnum punctuation context sensitive — https://github.com/rsms/inter/issues/647 - The hyphen/hyphen.case.tf are too overspaced — https://github.com/rsms/inter/issues/740 - The tabular figures' advance width in Regular weight do not match the other masters' — https://github.com/rsms/inter/issues/741 - Regular master tnum width 1328, other 5 masters are 1320 — https://github.com/rsms/inter/issues/904 - Tabular numbers not monospaced in Black, Bold and Medium — https://github.com/rsms/inter/issues/60 - Tabular numbers not working when importing from Google Fonts — https://github.com/rsms/inter/issues/245 - Tabular numbers don't seem to work with the WOFF2 file (discussion) — https://github.com/rsms/inter/discussions/813 ## Question - Is there an estimated timeline for v4.2 / the `cv15` release? - Would the maintainers consider shipping `cv15` as a point release or webfont build ahead of a full v4.2, given it's already merged? ## References - #557 — https://github.com/rsms/inter/issues/557 - #579 — https://github.com/rsms/inter/issues/579 - Commit: a264bbeSource: rsms/inter