Documentation Index
Fetch the complete documentation index at: https://docs.yamuno.com/llms.txt
Use this file to discover all available pages before exploring further.
Known Issues & Limitations
1. External Images and Attachments Require Whitelisting
Issue: Images loaded from external URLs (e.g.<img src="https://example.com/image.png">) are blocked in Block all and Whitelist modes unless the domain is whitelisted.
Workaround: Add the image host domain to the whitelist, or host images as Confluence attachments and reference them via their Confluence attachment URL.
2. Confluence Attachments Not Directly Accessible
Issue: Due to Atlassian’s data egress policy, you cannot directly reference Confluence attachment URLs inside the macro iframe using relative paths. Workaround: Use the full absolute Confluence attachment URL (e.g.https://yoursite.atlassian.net/wiki/download/attachments/...).
3. iframe Isolation
Issue: JavaScript inside the macro runs in an isolated iframe and cannot access the parent Confluence page DOM, cookies, or local storage. Workaround: This is by design for security. If you need to interact with Confluence page data, use the Confluence REST API from within your script.4. No Server-Side Code
Issue: HTML Macro only runs client-side code (HTML, CSS, JavaScript). Server-side languages (PHP, Python, etc.) are not supported. Workaround: Use external APIs or serverless functions to handle server-side logic and call them from JavaScript inside the macro.5. Print / PDF Export
Issue: Confluence’s built-in PDF export and print functions may not render the HTML Macro content correctly, as iframes are not always captured by browser print engines. Workaround: Use PDF Exporter for Confluence for PDF exports that need to include macro content.If you encounter an issue not listed here, please contact our support team.