quarto-dev / quarto-dev/quarto-cli
output-location: column does not work with tabsets
Nessuno ha ancora preso questa issue.
- Lingua principale
- JavaScript
- Stelle
- 6k
- Fork
- 458
- Merge medio
- 1g 9h
- PR unite (30g)
- 41
Descrizione
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!
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- r
- Ambito
- frontend, web-dev
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 45/100