You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Startup can hang when Page.enable runs after navigation #481
Context: my team has some code that calls kaleido from within CI jobs (via to_image on a Plotly figure object). Sometimes this was hanging forever, which I think was due to a startup race in Kaleido.
Here's my findings:
_KaleidoTab.navigate() sends Page.navigate before Page.enable. If the page finishes loading before Page events are enabled, Page.loadEventFired is missed and navigation waits indefinitely.
The attached kaleido_navigation_race.py reproduces this with Kaleido 1.5.0 and Choreographer 1.4.0 by inserting a two-second delay after Page.navigate returns. At that point, document.readyState is complete; the Runtime context future completes, but the Page load future remains pending until the repro cancels it.
The script also demonstrates that enabling Page events before navigation avoids the hang under the same delay. The existing comment suggesting that completed events are replayed appears incorrect for Page.loadEventFired.
Activity
camdecoster commentedon Oct 19, 2026
I'll provide feedback in your PR.
dennisjlee commentedon Nov 2, 2026
@camdecoster thanks for the review on this! Do you know when this would get included in a release to pypi?
Enable page events before navigation in PNG export
Enable page events before navigation in PNG export
camdecoster commentedon Nov 12, 2026
@dennisjlee this was just released in 1.5.1.