quarto-dev / quarto-dev/quarto-cli
Footnote/{.aside} from code annotation list HTML render bug.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
If you change between short footnote (^[footnote text]) and aside ([Text put in marging]{.aside}) both render really badly.
The code annotation list isn't put in the main text entry column.
---
project:
type: website
output-dir: docs
website:
title: "A Somewhat Gentle Introduction to Haskell"
navbar:
left:
- href: index.qmd
format:
html:
code-annotations: true
code-line-numbers: false
code-overflow: scroll
code-fold: false
# Gettin muh tufte on
reference-location: margin
citation-location: document
tbl-cap-location: margin
cap-location: margin
---
```{.haskell}
fact :: Int -> Int -- <1>
fact 1 = 1 -- <2>
fact n = n * (fact (n-1)) -- <3>
```
1. This is the *type signature* of the function. It says that it takes an `Int` (the first mention) and returns (the second mention) an `Int`.
2. Base case, but only for the number `1`. To cover `0`, either add a similar line or solve it with guards^[The implementation of `takeWhile` in the list of exercise uses guards. Keep a lookout!].
3. The n to the left of `=` is the argument to the function. Everything on the right side of `=` is the "return" expression.
Quarto check output
Latest git version. All dependencies except R installed.
git show -s --format="%as %H"
2024-08-29 a2430bedc2c070bf7997eeabc8ab20148576d967
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the supplied Quarto Markdown example with HTML code annotations enabled and compare the rendered output when the footnote is changed to an aside. Inspect the HTML rendering paths for code annotation lists, footnotes, and asides. Done means the annotation list remains in the main text entry column in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- 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