Our CSS font stack of monospace styled elements varies across web products without reason.
We should unify rules to one approach, best probably [[ https://github.com/necolas/normalize.css/blob/73b6b0c7e8690ab5005bca9d7e13d3fb319c98ac/normalize.css#L145 | `font-family: monospace, monospace``font-family: monospace, monospace` [[ https://github.com/necolas/normalize.css/blob/73b6b0c7e8690ab5005bca9d7e13d3fb319c98ac/normalize.css#L145 | as used in normalize.css ]].
Background of this CSS value is to tackle different [[ https://github.com/necolas/normalize.css/issues/519 | cross-browser monospace font sizing quirks, see detailed explanation ]].
Original comparison by @matmarex in T175709#3630249
> These two versions are exactly equivalent, I don't think we've been using any of the possible variants of this hack consistently. I grepped core and extensions and found the following number of usages:
>
> | Rule | Usages |
> | -- | -- |
> | `font-family: monospace, 'Courier';` | 18 |
> | `font-family: monospace, monospace;` | 8 |
> | `font-family: monospace, fixed;` | 2 |
> | `font-family: monospace, 'Courer New';` | 1 |
Also, @Edokter has introduced a MW core comparison at {T35496}