-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Disable size containment for split handle #560
Conversation
@@ -18,6 +18,8 @@ | |||
|
|||
.lm-SplitPanel-handle { | |||
z-index: 1; | |||
/* disable size containment as the handle overhangs another div */ | |||
contain: style!important; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
contain: style!important; | |
contain: style !important; |
Unless it's meaningful to have style!important
as one contiguous token, adding a space would make this more readable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is using !important here OK because essentially we never want the style to be overwritten by anything?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good question. In JupyterLab it would be ok with the logic "we are overriding lumino and changing widget setting to not use strict containment in JS is not worth the trouble". But here we are modifying core lumino so maybe another fix by not adding contain: strict
would be better. I will need to check if we can do so without breaking API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So instead of adding this style we should just remove this line:
lumino/packages/widgets/src/splitlayout.ts
Line 832 in 133d872
handle.style.contain = 'strict'; |
Thanks for questioning me - the identification of the problem was right but solution was wrong, another reason not to make PRs at 3am even if those are as simple as 2 lines :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or rather we should change strict
to style
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problems! I've searched for !important in Lumino before asking and it is used in couple of places in the codebase. Thanks for fix and explanations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's merge this (I don't have access / rights to merge) |
@krassowski wanted to ask what needs to be done to put lumino with #560 merged into jupyterlab? Is it something like lumino new release --> update jupyterlab dependencies? |
Yes. We have |
Fixes jupyterlab/jupyterlab#14219