quarto-dev / quarto-dev/quarto-cli

Document path expectations for non-project documents

Open
#8,805 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What is wrong

When the render button in RStudio is used to render a qmd file to .html the images (whether they are embedded via Markdown or with R code via knitr::include_graphics) do not display in the HTML preview in the viewer pane. However the images are visible in the notebook/.qmd in the editor, and when the .html file is opened in a web browser. See screenshots:

Screenshot 2024-02-15 at 6 07 25 PM Screenshot 2024-02-15 at 6 07 39 PM
What is the expected behaviour

Any images/figures correctly embedded with either Markdown or with R code via knitr::include_graphics should be visible in the HTML preview in the viewer pane.

Environment information
  • Mac (Version 13.4 (22F66))
  • RStudio (Version 2023.12.1+402 (2023.12.1+402))
  • R (version 4.3.2)
  • Quarto (version 1.3.450)

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.

Research direction

Reproduce the problem by using RStudio's render button on a qmd document containing Markdown images and knitr::include_graphics, then compare the HTML in the viewer pane with the browser preview. Trace how the rendered document and image paths are handled for non-project documents; done means both image types display in the viewer pane as they do in the browser.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.