quarto-dev / quarto-dev/quarto-cli
Failure of multiple inline OJS elements with inline style
Offen
@cscheid arbeitet bereits daran.
Seit 10.5.2023.
bug
ojs-engine
- Vorherrschende Sprache
- JavaScript
- Sterne
- 6k
- Forks
- 458
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 41
Beschreibung
Having more than one inline OJS element ${x} combined with inline styling [foo]{style="color:red;"} fails to render properly, although it works having more than one of one or the other, and having one element combining both.
```{r}
ojs_define(x = "inline OJS")
```
Multiple inline OJS elements in a single paragraph work: ${x} and ${x}.
Multiple [inline]{style="color: red;"} styles [work]{style="color: red;"}.
One [${x}]{style="color: red;"} element with inline style works in the same paragraph as another [inline style]{style="color: red;"}.
One [${x}]{style="color: red;"} element with inline style works in the same paragraph as another non-styled ${x} element.
One [${x}]{style="color: red;"} element with inline style **does not work** in the same paragraph as another styled [${x}]{style="color: red;"} element.
This is with sessionInfo():
R version 4.3.0 (2023-04-21)
Platform: aarch64-apple-darwin20 (64-bit)
Running under: macOS Ventura 13.0
Matrix products: default
BLAS: /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/lib/libRlapack.dylib; LAPACK version 3.11.0
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
time zone: Europe/Vienna
tzcode source: internal
attached base packages:
[1] stats graphics grDevices utils datasets methods base
loaded via a namespace (and not attached):
[1] htmlwidgets_1.6.2 compiler_4.3.0 fastmap_1.1.1 cli_3.6.1
[5] tools_4.3.0 htmltools_0.5.5 rstudioapi_0.14 yaml_2.3.7
[9] rmarkdown_2.21 knitr_1.42 xfun_0.39 digest_0.6.31
[13] jsonlite_1.8.4 rlang_1.1.1 evaluate_0.21
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.