moorepants
commented
4 years ago Every time the editing popup modal is opened it should connect to the same kernel associated with that page. The restart button in the popup modal is problematic because if you press it and you had prior executed cells, you can't rerun those cells. Jupyter notebook and jupyter lab both have a button that runs all cells in order up to the one you are editing. If we had that same button in the popup modal, then you could press "Restart and run all cells before this one" type of command.
When editing a Libretexts page (click the edit button at the top of the page), there is no way to run or restart a code cell like you would when viewing the page normally. These process are only possible while actively editing a single given cell. As a result, that kernel and the associated data running through it are all isolated to that code cell instance. This means that debugging becomes very difficult when trying to "chain" together multiple code cells which depend on each other. We would need to discuss and find a way to get the kernel to persist across the entire page while editing, just as it does when you are viewing the page normally. This also means finding some way to run/restart code cells while editing and not actively in the single cell editor window. Honestly, it probably requires a complete overhaul of our current editing ui.