quarto-dev / quarto-dev/quarto-cli

`monobackgroundcolor` ignored by document title and section title

Open
#6,781 3 comments 0 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Apr 8, 2025.

enhancement html themes
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

As the title suggests, monobackgroundcolor seems to be ignored by by document title and section title.

Steps to reproduce
---
title: "Document title with `code`"
format:
  html:
    monobackgroundcolor: "transparent"
---

# Section title with `code`

Some text with `code`
Expected behavior

monobackgroundcolor should affect document title and section title as well.

Actual behavior

monobackgroundcolor does not affect document title or section title. Example below:

图片

Your environment
  • IDE: RStudio 2023.06.0 Build 421
  • OS: Ubuntu 22.04
Quarto check output
quarto check

[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.1: OK
      Dart Sass version 1.55.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.3.361
      Path: /opt/quarto/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.10.12
      Path: /usr/bin/python3
      Jupyter: (None)

      Jupyter is not available in this Python installation.
      Install with python3 -m pip install jupyter

[✓] Checking R installation...........OK
      Version: 4.3.0
      Path: /usr/lib/R
      LibPaths:
        - /home/nick/R/x86_64-pc-linux-gnu-library/4.3
        - /usr/local/lib/R/site-library
        - /usr/lib/R/site-library
        - /usr/lib/R/library
      knitr: 1.43
      rmarkdown: 2.22

[✓] Checking Knitr engine render......OK

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.