quarto-dev / quarto-dev/quarto-cli
Reference in lightbox caption not rendered
Open
@cscheid is already working on this.
Since Oct 9, 2024.
bug
citations
lightbox
needs-discussion
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
A reference in a lightbox caption is not being rendered.
Steps to reproduce
---
title: "Lightbox test"
format: html
lightbox: true
references:
- id: fenner2012a
title: One-click science marketing
author:
- family: Fenner
given: Martin
orcid: 0000-0003-1419-2405
container-title: Nature Materials
volume: '11'
URL: 'http://dx.doi.org/10.1038/nmat3283'
DOI: '10.1038/nmat3283'
issue: '4'
publisher: Nature Publishing Group
page: 261-263
type: article-journal
issued:
date-parts:
- - 2012
- 3
---
![Some claim [@fenner2012a].](48881397073_c189eba6a9_q.jpg)
Expected behavior
Actual behavior
Your environment
- IDE: RStudio 2024.07.0 Build git.copr7652421
- OS: Fedora 40
Quarto check output
quarto check
Quarto 1.6.9
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.2.0: OK
Dart Sass version 1.70.0: OK
Deno version 1.41.0: OK
Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.6.9
Path: /home/<USER>/bin/quarto/bin
[✓] Checking tools....................OK
TinyTeX: (not installed)
Chromium: (not installed)
[✓] Checking LaTeX....................OK
Using: Installation From Path
Path: /usr/local/texlive/2024/bin/x86_64-linux
Version: 2024
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.12.4
Path: /usr/bin/python3
Jupyter: 5.7.1
Kernels: ir, python3
[✓] Checking Jupyter engine render....OK
[✓] Checking R installation...........OK
Version: 4.4.1
Path: /usr/lib64/R
LibPaths:
- /home/<USER>/R/x86_64-redhat-linux-gnu-library/4.4
- /usr/local/lib/R/library
- /usr/lib64/R/library
- /usr/share/R/library
knitr: 1.48
rmarkdown: 2.28
[✓] 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.