-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
footer icons need HTML, which prevents extensions from resolving assets #9473
Comments
In the case of the addition of |
FYI, markdown works in page-footer:
right:
- text: "![](/images/posit-logo-black-TM.svg){#footer-right-posit-logo width=100px}"
href: "https://posit.co" Although, Quarto will raise a warning: WARNING (src/resources/filters/./quarto-pre/parsefiguredivs.lua:517) Figure with invalid crossref category: footer-right-posit-logo
Won't be able to cross-reference this figure. |
We're raising a warning because of the dashes being used here. (We've considered removing this warning because it causes too many false positives like that. I'll probably do it right now.) |
@mcanouil - I cannot replicate your |
The example was mostly about the statement saying that HTML is required. The main issue with assets inside extension is how to tell Quarto how to find them, both when creating an extension and using them. |
It would be nice if Quarto could look for resources inside extensions without having to set "_extensions/account/ext-name" (path if installed using |
For reference: |
Bug description
An extension defining a custom project type wants to declare a shared footer and use some images as icons within that footer. For example:
If the page footer supported an
image
attribute and took an image path, the in-extension path could be resolved without resorting to HTML.My understanding is that Quarto does not attempt to resolve asset paths within text, but can do so for fields which are known to contain file references.
Steps to reproduce
No response
Expected behavior
No response
Actual behavior
No response
Your environment
No response
Quarto check output
The text was updated successfully, but these errors were encountered: