Closed ianalis closed 7 months ago
I can reproduce. Changing editable status works well, but upon re-opening the notebook the cell is in fact editable.
This is an interesting case. There is no obvious fault on jupyterlab-execute-time side. This can be traced to switching the recordTiming
setting in line 61 here:
However, changing this setting manually does not lead to this side-effect.
Briefly, programatically changing a notebook tracker setting triggers refresh of editorConfig
, which removes the readOnly
flag because it has "special" handling (the read-only status come from the model rather than from the user settings).
I found a way to reproduce this in core JupyterLab (which also changes settings programatically in some code paths) and opened an issue over there: https://github.com/jupyterlab/jupyterlab/issues/15514
Closing in favor of https://github.com/jupyterlab/jupyterlab/issues/15514.
Cells can be made read-only by adding
"editable": false
to the cell metadata. The contents of the read-only cell can still be selected and the cursor can still be placed in it but the content cannot be modified or added:However, if
jupyterlab-execute-time
is installed, the content of the read-only cell becomes editable:The test system I used to generate the screenshots has the following (selected) installed packages:
The production system where I discovered the problem has the following (older) versions: