quarto-dev / quarto-dev/quarto-cli
`table-striped` is invisible in `darkly` HTML theme
Open
@cscheid is already working on this.
Since Jun 21, 2024.
bug
themes
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
Perhaps I was expecting too much, and have verified it works in the default theme. I am using darkly and the striped visually appears to have no effect.
Steps to reproduce
_quarto.yml
---
project:
type: website
format:
html:
theme: darkly
index.qmd
---
format: html
listing:
contents: .
table-striped: true
type: table
---
a.qmd
---
title: A
format: html
---
b.qmd
---
title: B
format: html
---
Expected behavior
I would expect alternating black and some shade of grey perhaps?
Actual behavior
All rows appear essentially the same - works in default theme
Your environment
No response
Quarto check output
Quarto 1.4.555
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.1.11: OK
Dart Sass version 1.69.5: OK
Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.4.555
Path: /Applications/quarto/bin
[✓] Checking tools....................OK
TinyTeX: (not installed)
Chromium: (not installed)
[✓] Checking LaTeX....................OK
Using: Installation From Path
Path: /Users/paddy/texlive/2024/bin/universal-darwin
Version: 2024
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.12.4
Path: /Users/paddy/arc/misc/python-tooling/.venv/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.4.1
Path: /opt/homebrew/Cellar/r/4.4.1/lib/R
LibPaths:
- /opt/homebrew/lib/R/4.4/site-library
- /opt/homebrew/Cellar/r/4.4.1/lib/R/library
knitr: 1.47
rmarkdown: 2.27
[✓] Checking Knitr engine render......OK
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.