Callouts at page bottom are split across two pages.

Open
#14,496 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
cli, content

Research direction

Start by reproducing the issue with the attached index.md and callout_contents.md files using the documented quarto preview command. Compare the generated PDF and DOCX outputs, then trace the callout pagination behavior and identify where an automatic page break could be applied. Done means short callouts no longer split across pages in both formats, with the reported behavior verified.

Written by the indexing model from the issue text.

Description

bug latex
I have:
  • searched the issue tracker for similar issues
  • installed the latest version of Quarto CLI
  • formatted my issue following the Bug Reports guide
Bug description

Callouts placed at the bottom of the page that are shorter than the page height are split across two pages, which looks unprofessional.

Steps to reproduce
  1. Create a new project via quarto create project manuscript quarto-individual-callout-placement
  2. Copy the attached ìndex.md and callout_contents.md into the project directory. Replce the existing ìndex.qmdwithindex.md` via rename.
  3. Preview the project via quarto preview quarto-individual-callout-placement/ --render all --debug
  4. Check the placement of the callouts in the resulting PDF and MS Word (DOCX) outputs.

callout_contents.md

index.md

Actual behavior

If a callout begins just before the end of the page, it will be split across the current page and the next page.

This is true for PDF and DOCX. Other formats have not been checked.

Expected behavior

It would be much more advantageous to place an automatic {{< pagebreak >}} before such callouts if there is not enough space before the end of the page. It should be possible to disable this behavior via the callout’s configuration (in case of potential issues).

Your environment
  • OS: Linux
  • IDE: None
Quarto check output

Quarto 1.9.37
[✓] Checking environment information...
Quarto cache location: /home/mint/.cache/quarto
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.8.3: OK
Dart Sass version 1.87.0: OK
Deno version 2.4.5: OK
Typst version 0.14.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.9.37
Path: /opt/quarto/bin

[✓] Checking tools....................OK
TinyTeX: v2026.04
Chromium: (not installed)
Chrome Headless Shell: (not installed)
VeraPDF: (not installed)

[✓] Checking LaTeX....................OK
Using: TinyTex
Path: /home/mint/.TinyTeX/bin/x86_64-linux
Version: 2026

[✓] Checking Chrome Headless....................OK
Using: Chrome found on system
Path: /usr/bin/google-chrome
Source: PATH

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

[✓] Checking R installation...........(None)

  Unable to locate an installed version of R.
  Install R from https://cloud.r-project.org/

[✓] Checking Python 3 installation....OK
Version: 3.12.3
Path: /home/mint/Desktop/quarto-env/bin/python3
Jupyter: 5.9.1
Kernels: python3

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

[✓] Checking Julia installation...

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

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.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.