zyratlo opened a new issue, #8908: URL: https://github.com/apache/texera/issues/8908
### What happened? The Jupyter panel is meant to be a read only reference view of the source a workflow was generated from. Its cells start out read only, but clicking into any cell makes that cell editable. After the click, typing changes the cell and keyboard shortcuts such as Shift+Enter (run cell) and `d d` (delete cell) work again. Two causes: 1. Classic Notebook resets each editor's `readOnly` option from `cell.is_editable()` whenever the editor gets focus, and it re-enables the keyboard manager at the same time. `custom.js` sets `readOnly` once, so the first focus undoes it. 2. `custom.js` loads asynchronously, alongside the notebook, and usually runs after `notebook_loaded` has already fired. Its read only setup only took effect because it is also bound to `kernel_ready`. A notebook that opens without a kernel never gets it at all. A related symptom has the same root: a notebook whose kernel is not installed in the Jupyter image (an R notebook, for example) opens with a "Kernel not found" dialog over the panel. `custom.js` runs too late to suppress it. Expected: cells cannot be edited, executed, added or deleted, and no kernel dialog appears, whether or not a kernel starts. ### How to reproduce? 1. Generate a workflow from a notebook with the AI Generate Workflow tool and open it. 2. In the Jupyter panel, click inside any code cell and type. The text changes. 3. Press Shift+Enter. The cell runs. ### Version/Branch 1.4.0-incubating-SNAPSHOT (main) ### Commit Hash (Optional) _No response_ ### What browsers are you seeing the problem on? Firefox ### Relevant log output ```shell ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
