[giri256]

Fixes #1934.

Summary

• reset print-only content variables to mdBook's existing light palette
• keep all selected screen themes unchanged
• cover page, text, quotes, tables, keyboard keys, footnotes, and callouts through the shared variables

Verification

• Chrome print-media computed-style matrix for ayu, coal, light, navy, rust, and no-JavaScript navy
• navy screen-media negative control
• cargo test -p mdbook-html --lib
• cargo fmt --check
• git diff --check

[GuillaumeGomez]

Instead of redefining the variables, would be simpler to find a way to reuse the light variables from variables.css.

[giri256]

Good point, done in 29ef7f0. print.css no longer repeats the palette. In variables.css, the dark themes (ayu, coal, navy, rust, and the no-JS prefers-color-scheme: dark block) now only apply to @media screen, and the light block also matches :where(:root) as a zero-specificity fallback. When printing, no dark theme matches, so the light variables apply whatever theme is selected. On screen nothing changes.

Most of the diff is re-indentation (git diff -w is +8/-2). I checked it by building a book with default-theme = "coal": the screen stays coal and the printed PDF uses the light palette, same as before. cargo test passes.

One trade-off: a custom theme defined only through additional-css still applies when printing, because it isn't inside the screen blocks. The previous print.css override covered that case. I'm happy to go either way.

[rustbot]

☔ The latest upstream changes made this pull request unmergeable. Please resolve the merge conflicts.