iodide-project / iodide-project/iodide
Render MD chunks before evaling js
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
### What I Did
Here's a sample notebook, the report view should show "not working" but the "run full notebook" should show "autorun works": https://alpha.iodide.io/notebooks/2753/?viewMode=report
### What I Expected
The "Run Full Notebook" and "Report view" should produce the same output
### What Happened
From what I see, it's maybe because the HTML didn't load before the JS is executed, maybe I should wait on "onload" before querying the DOM
### (if applicable) notebook that reproduces bug
https://alpha.iodide.io/notebooks/2753/?viewMode=report
Contributor guide
Research direction
Reproduce the issue with notebook 2753 in Report view, then compare its output with Run Full Notebook. Trace the Markdown rendering and JavaScript evaluation order; done means both modes produce the same output, including “not working” versus “autorun works”.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100