HTML Export file just shows title, other slides are empty.
Describe the bug See title
To Reproduce Export a Story as HTML, open HTML in browser (Tried Safar, Firefox, Chrome and Arc)
Expected behavior Story plays like in preview on Story Canvas in Egon.io
Screenshots
Version
- Egon: v2.4
- Browser: Arc 1.79.1, Opera 114.0.5282.102, Safari 18.2, Chrome 132.0.6834.160
- OS: MacOS Sequoia 15.2
Hi, I could not reproduce the problem. Could you please attach the Domain Story as .egn file and the .html file?
Sure: domain_story_test.zip
Seems like the HTML export cannot handle diagrams that are outside of the visible are of the canvas. Let me explain:
%%{init: {"themeVariables": {"quadrant4Fill": "#a4d7e1"} }}%%
quadrantChart
title Coordinate Plane of the diagram-js Canvas
x-axis "-x" --> "+x"
y-axis "+y" --> "-y"
quadrant-1 "angle: 1° to 90°"
quadrant-2 "angle: 91° to 180°"
quadrant-3 "angle: 181° to 270°"
quadrant-4 "angle: 271° to 360°"
"(x: 0/ y: 0)": [0.5, 0.5]
Per default, the visible area of the canvas is the bottom right quadrant (+x/+y). That means that 0/0 is in the top left corner of the screen. You've probably scrolled the canvas before creating the diagram. In the development version of Egon, we've integrated a "mini map" that helps you to navigate around the canvas and find (parts of your) story that are outside the visible area.
The HTML file contains the diagram, but again its positioned outside the visible area. Scrolling doen't work in the HTML file, so there is no way of bringing the diagram back to the visible part. We should fix that.
Nope, didn't scroll, just threw in the actor and two items for the test. But thanks for the quick explanation, hope the fix is an easy one.
Just a question: When do you think this will be fixed? As the HTML export is a major feature we'll be using in our context, as this allows easy access for new users in our documentation process.
I can't give a reliable estimate. Have you considered exporting as animated SVG instead?
Kinda works for the moment. Thx for the hint.
Hey I just looked over the 3.0 beta notes and didn't find this issue solved there. Is this still on the roadmap for the v3?
Hi, I'm afraid we've just postponed this to a future v3.0.1 release.