font-variant-numeric Tabular/Lining Lookup
Supported font-variant-numeric axis combinations; tabular advances vs lining glyph form are independent, font support external. Explicit supplied computed/layout context only; not a browser cascade/layout engine or cross-browser guarantee.
Description
Numeric font features distinguish digit width and digit form.
Numeric font features distinguish digit width and digit form.1
A requested feature only affects rendering when the selected font supplies it. Use font-variant-numeric Tabular/Lining Lookup to look up a supported term.
When to use font-variant-numeric Tabular/Lining Lookup
Use font-variant-numeric Tabular/Lining Lookup to look up a supported term. Choose the exact supported token from the table; preserve its punctuation and capitalization.
How to use font-variant-numeric Tabular/Lining Lookup and understand its results
- Choose the exact supported token from the table; preserve its punctuation and capitalization.
- Enter Numeric policy using the field table and validation rules below, then run the tool.
- Read Meaning and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| numericPolicy | Numeric policy | string | Required; constraints below |
Enter one of the exact supported numericPolicy tokens in the table below. The implementation performs a case-sensitive lookup and returns the stored meaning without interpreting a stylesheet, audio recording or performance. Unsupported tokens, added whitespace and alternate capitalization are input errors. The entries describe a bounded vocabulary rather than every valid value in the wider topic.
meaning = storedTable[exactSupportedToken] Field order, units and branch conditions follow the implementation explanation above.
| Exact supported token | Stored meaning |
|---|---|
| tabular-lining | tabular-nums lining-nums |
| proportional-lining | proportional-nums lining-nums |
| tabular-oldstyle | tabular-nums oldstyle-nums |
| proportional-oldstyle | proportional-nums oldstyle-nums |
| Output field | Meaning | Value type |
|---|---|---|
| meaning | Stored explanation for the exact supported token. | string |
{
"input": {
"numericPolicy": "tabular-lining"
},
"output": {
"meaning": "tabular-nums lining-nums"
}
}Limitations and assumptions
A requested feature only affects rendering when the selected font supplies it. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use image-rendering:pixelated Integer Scale Note for a related task: Integer scaling can map one source pixel to a uniform number of display pixels.
Use font-feature-settings Ligatures Toggle for a related task: Ligature settings request particular OpenType feature tags.
References
Similar or alternative tools
- image-rendering:pixelated Integer Scale Note
Integer scaling can map one source pixel to a uniform number of display pixels.
- font-feature-settings Ligatures Toggle
Ligature settings request particular OpenType feature tags.