/**
 * List numbers in the same digits as the text beside them.
 *
 * Teamwork 49828371: on /resource/sahp-restorative-care-pathway the "2." and
 * "3." of a numbered list came out faint grey for the client on Windows
 * (Chrome and Edge), while 1, 4, 5 and 6 looked normal. On a Mac all six look
 * the same, and the list's HTML is six identical <li>s.
 *
 * WHY. Browsers draw list numbers with tabular figures: the user agent sheet
 * gives `::marker` `font-variant-numeric: tabular-nums`. In NB International
 * Pro Book (NBInternationalProBoo.woff2, the body weight) four of those
 * tabular glyphs, zero.tnum, two.tnum, three.tnum and nine.tnum, carry their
 * outline twice, the same contour laid exactly over itself. macOS fills the
 * overlap as solid. Windows' rasteriser cancels the two copies out and leaves
 * only the anti-aliased edge, which is the faint, colour-fringed ghost in the
 * screenshots. The proportional digits the text uses are drawn once and are
 * fine, which is why the "3" in "Module 3:" on the same list renders normally.
 * The other weights (Light, Medium, Medium Italic, Bold) have no such glyphs.
 *
 * So every numbered list in body copy is affected on Windows: 2, 3, 9, 10, 20
 * and so on. Editing the font file is not ours to do under its licence, so the
 * fix is to stop asking for those glyphs. Markers take the proportional digits
 * the text already uses. It also ends a smaller mismatch: the tabular "1" has a
 * foot the proportional "1" does not (see the note in ota-search.css), so the
 * "1." of a list was a different glyph from every 1 in the copy beside it.
 * Numbers in a list do not need to line up in a column; the marker box is
 * right-aligned to the text either way.
 *
 * @package Agend\OTA
 */

::marker {
	font-variant-numeric: normal;
}
