diff options
author | Andrew Jorgensen <andrew@jorgensenfamily.us> | 2021-08-12 23:42:04 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-08-13 08:42:04 +0200 |
commit | 2fa45b92a24e76a610f86f1e039225be5d8cb695 (patch) | |
tree | ee0bb542381238551b6dc98aef7305ebbc965719 /exampleSite | |
parent | 78c5241a8ef4f90d9944eed0c7429504d4ca6c15 (diff) | |
download | hugo-bearcub-2fa45b92a24e76a610f86f1e039225be5d8cb695.tar.gz hugo-bearcub-2fa45b92a24e76a610f86f1e039225be5d8cb695.tar.bz2 |
Fix a remaining issue with b8c8871 (#20) (#25)
It turns out my original proposal for #20 was correct, but not for the
reasons I thought. We need to set both `background-color` and `color` to
`initial` on `div.highlight pre` because that's where Chroma sets those
colors (including the default `color` if configured). Setting to
`initial` there makes it so that if the selected style *doesn't*
configure a default color, we'll use the `initial` color, which is going
to be the right choice because the reason style author left that unset
because they didn't consider dark color schemes messing with their
style. Then we `unset` the colors on `div.highlight code` because
otherwise the `code` colors from the theme will override the colors that
would otherwise be inherited from Chroma's `<pre>` element.
Stricly speaking I can't say that setting `background-color` to
`initial` is required, because I haven't found a Chroma style that
*doesn't* set a `background-color`, but I figure it's possible (at least
for a light theme) and it makes sense to fix it just in case, and causes
no harm otherwise.
Diffstat (limited to 'exampleSite')
0 files changed, 0 insertions, 0 deletions