Read-only cells are not enforced if jupyterlab-execute-time is installed about jupyterlab-execute-time

[krassowski]

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:

jupyterlab-execute-time/src/ExecuteTimeWidget.ts

Lines 57 to 61 in a282046

	this._settingRegistry
	.load('@jupyterlab/notebook-extension:tracker')
	.then(
	(nbSettings: ISettingRegistry.ISettings) =>
	nbSettings.set('recordTiming', true),

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: jupyterlab/jupyterlab#15514

[krassowski]

I can reproduce. Changing editable status works well, but upon re-opening the notebook the cell is in fact editable.

[mlucool]

Closing in favor of jupyterlab/jupyterlab#15514.