-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Header part not reflecting Jupyter Notebook Top Area default setting #6833
Comments
jupyterlab-probot
bot
added
the
status:Needs Triage
Applied to issues that need triage
label
Apr 5, 2023
Thanks @yumyumqing for opening this issue and providing all the details 👍
Would you like to open a draft PR so we can see how that would work?
I don't recall exactly why it is like this. But this git history seems to be pointing to this commit: 6c96c80 |
yumyumqing
added a commit
to yumyumqing/notebook
that referenced
this issue
Apr 6, 2023
* The header part was only reflecting user preference but not default settings overrides.
yumyumqing
added a commit
to yumyumqing/notebook
that referenced
this issue
Apr 7, 2023
* The header part reflects both user preference and default settings overrides. * Toggle 'Show Header' turns off the automatic adjustment.
yumyumqing
added a commit
to yumyumqing/notebook
that referenced
this issue
Apr 14, 2023
* The header part reflects both user preference and default settings overrides. * Toggle 'Show Header' turns off the automatic adjustment.
yumyumqing
added a commit
to yumyumqing/notebook
that referenced
this issue
May 2, 2023
* The header part reflects both user preference and default settings overrides. * Toggle 'Show Header' turns off the automatic adjustment.
yumyumqing
added a commit
to yumyumqing/notebook
that referenced
this issue
May 2, 2023
* Make 'visible' enum type and pick up both default and user settings.
jtpio
pushed a commit
that referenced
this issue
May 3, 2023
Fixed with PR #6836 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
In settings editor,
Jupyter Notebook Top Area
is only reflecting changes fromUser Preferences
but notSettings Overrides
.When I start the jupyter notebook with default settings overrides, the menu does pick up the
visible: false
setting, but the notebook is still showing header part.If I toggle the setting manually by clicking the box, the change does reflect in the notebook header part.
But then if I click
Restore to Defaults
, the notebook header is not picking up the change again.To Reproduce
Steps to reproduce the behavior:
overrides.json
file insettings
dir in JupyterLab Application Directory.If using
mamba
as step 1, the dir should look something like$HOME/mambaforge/envs/notebook/share/jupyter/lab/settings
.jupyter notebook
in dev modejupyter notebook
Settings
-Settings Editor
-Jupyter Notebook Top Area
not
checkedheader
is still showingsetting
page andcheck
the box anduncheck
againheader
isnot
showing nowsetting
page andcheck
the box and then clickRestore to Defaults
header
isstill
showingExpected behavior
In my opinion, I think the
header
part should reflect the default settings (if there is noUser Preference
) for 2 reasons:jupyterlite
, that uses this plugin but does not supportUser Preference
override, it would be hard for the users to hide theheader
part by default.(I think
jupyterlite
uses browser cache forUser Preference
settings and does not allow overrides at build time. Please correct me if I am wrong on this.)Screenshots
Desktop (please complete the following information):
Additional context
I think the reason for the bug might come from these 2 places:
updateSettings
is only changing top visibility when there isUser Preference
set up. This should probably be outside of the user setting check.notebook/packages/application-extension/src/index.ts
Lines 497 to 499 in 1512c82
User Preference
isn't set up, the plugin will adjust the header showing based on screen size only.notebook/packages/application-extension/src/index.ts
Lines 519 to 528 in 1512c82
If we fix the bug as in Expected behavior, this neat feature of adjusting based on screen size might go away.
If we still want to keep the adjustment, maybe we can have another variable to flag whether we would like to do adjustment like
adjustToScreen: true
which could overrides the header settings.Thanks for taking a look!
The text was updated successfully, but these errors were encountered: