-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Various JupyterLab UI bugs #1944
Comments
Today I don't see the text in terminal disappearing bug (though I saw it all the time late last week), but the keyboard shortcuts issue remains. I think it affects all JupyterLab notebook servers. A specific server affected is in the greenhouse-detection namespace, server process-sentinel. |
Unfortunately, this seems to be a feature of JupyterLab 4.0.x. I searched for a way of customizing keyboard shortcuts in JupyterLab and all I could find was: I also reached out to CodeMirror but they were not interested in changing anything. I guess they are trying to be more consistent with VS Code: |
Reposting message from Stan Hatko:
|
Placing back in backlog until Upstream fixed is provided. |
I've put the terminal text dissapearing issue into a separate issue: |
I'm watching jupyterlab/jupyterlab#14548. |
On new notebook servers ctrl+S and ctrl+F trigger browser actions in addition to the JupyterLab actions. As a workaround entering the following into the web developer console (in Edge) worked for me, disabling the browser action while keeping the Jupyter action. Code below from https://stackoverflow.com/questions/4446987/overriding-controls-save-functionality-in-browser and https://stackoverflow.com/questions/7091538/is-it-possible-to-disable-ctrl-f-of-find-in-page. document.addEventListener("keydown", function(e) {
if (e.keyCode === 83 && (navigator.platform.match("Mac") ? e.metaKey : e.ctrlKey)) {
e.preventDefault();
// Process event...
}
}, false);
window.addEventListener("keydown",function (e) {
if (e.keyCode === 114 || (e.ctrlKey && e.keyCode === 70)) {
e.preventDefault();
}
}) |
Stan Hatko wrote:
The text was updated successfully, but these errors were encountered: