quarto-dev / quarto-dev/quarto-cli

output-location: column does not work with tabsets

Open
#3,301 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi,

I am not sure if this is a bug or a feature, although but I have not been able to find it documented nor in other bugs reports.

I have Quarto document with output format revealjs. I include in my code chunks the options echo: true and output-location: column (the same happens with column-fragment).

It works as expected when in a regular slide. But if the code chunk in under panel tabset the output is not shown in an adjacent column, but below the code. Here is an example

---
title: "test"
format: revealjs
---

## Works as expected

Code in the left and `4` shown in an adjacent column.

```{r}
#| echo: true
#| output-location: column
2 + 2
```

## Tabset

::: {.panel-tabset}

### Tab 1

First tab

### Tab 2

Here output `4` is shown below the code

```{r}
#| echo: true
#| output-location: column
2 + 2
```
:::

Not sure if relevant in this case, but for completeness, I am using RStudio 2022.07.02 (build 576) with knitr engine under Linux (Lubuntu 22.10).

Thanks a lot in advance!

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

Start by reproducing the supplied document with the knitr engine and revealjs output, comparing the regular slide with the panel-tabset case. Trace how output-location: column and column-fragment are rendered inside tabsets. Done means code output appears in an adjacent column within both tabset and regular slides, with the existing example still working.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.