From d2f73298f42893d81af3da1084617a36ca6acca3 Mon Sep 17 00:00:00 2001 From: Jamie Tanna Date: Sun, 13 Oct 2024 14:43:47 +0100 Subject: [PATCH] docs: add fallback for `monospace` fonts The current CSS doesn't provide a `monospace` fallback in some cases, only using named fonts, which leads to systems without these fonts not presenting code snippets as monospaced. --- assets/stylesheets/print.css | 2 +- assets/stylesheets/stylesheet.css | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/assets/stylesheets/print.css b/assets/stylesheets/print.css index 541695b..4494c83 100644 --- a/assets/stylesheets/print.css +++ b/assets/stylesheets/print.css @@ -81,7 +81,7 @@ header h2 { } code, pre { - font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal; + font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; color: #222; margin-bottom: 30px; font-size: 12px; diff --git a/assets/stylesheets/stylesheet.css b/assets/stylesheets/stylesheet.css index 62b4ef1..7b58c10 100644 --- a/assets/stylesheets/stylesheet.css +++ b/assets/stylesheets/stylesheet.css @@ -170,7 +170,7 @@ a.button span { } code, pre { - font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal; + font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; color: #222; margin-bottom: 30px; font-size: 14px;