-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Bump to JupyterLab 4.1.0a4 bis #7172
Conversation
@jtpio I was not able to open this PR in your branch https://github.com/jtpio/notebook/tree/update-lab-410a4 I also don't know why there are conflicts here and not in #7166, since the conflicting files have been changed there... |
763111e
to
7e1bbc0
Compare
Thanks @brichet for picking this up!
It was mimicking the behavior of the classic notebook. With some buttons available depending on the number being selected and their type. Normally the rename button was already rendered when a single item was selected: |
Trying on Binder, it looks like the text content of the delete button is not visible by default: notebook-delete-button.webm |
Also we might need to tweak the CSS a bit so the hover button background takes the full height on hover: notebook-hover-buttons.webmCurrently with fileactions-buttons-hover.webmWe can also fix that separately, maybe it was introduced before in #7161. |
I tested it on chrome. We should probably add a snapshot including the delete button. |
display: none; | ||
} | ||
|
||
.jp-FileActions .jp-ToolbarButtonComponent[data-command='filebrowser:delete'] { | ||
.jp-FileBrowser-toolbar | ||
.jp-FileAction:has( |
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.
Looks like this might be the cause for the Firefox rendering issue? (with Firefox 118)
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.
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.
Thanks, this is indeed the issue.
We should probably use the ID of element.
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.
It should be fixed now, using the ID
Fixed in b7f24c6 |
Nice thanks @brichet. |
bot please update playwright snapshots |
I added a CSS rule for the 'New' menu (the text was not centered in the component). |
Kicking CI |
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.
Thanks @brichet!
This PR supersede #7166
Changes
CSS in toolbar to reflect the changes on toolbar components, following [Accessibility] Using arrow keys to navigate in toolbars items jupyterlab/jupyterlab#15021
Filebrowser toolbar
See Bump to JupyterLab 4.1.0a4 #7166 (comment) for context.
It changes the logic to include the action buttons in the filebrowser toolbar, and restore the previous appearance of the action buttons.
The action button in the filebrowser toolbar were included in an actions toolbar, which breaks keyboard-only usage (using tab and arrow keys).
With this PR, the buttons are included in the file browser toolbar as direct child.
NOTES:
rename
button. I didn't really understand the previous logic, now it's displayed if a single item is selected. Let me know if I should revert this change.