Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork3.8k
Add jump to executing/executed cell button#16880
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
Thanks for making a pull request to jupyterlab! |
for more information, seehttps://pre-commit.ci
Darshan808 commentedOct 18, 2024
@JasonWeill Can i get this PR labelled as 'hacktoberfest-accepted'. I would really appreciate it. |
…terlab into scroll-to-executing-cell
krassowski left a comment
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.
UX thoughts:
- how will user know that clicking here will cause scroll action? The label just says "kernel status"
- how can we add more actions in the future? If we make click on the indicator one thing we cannot make it another thing (except for alt + click etc combinations, but these won't work on touch screens)
I would like to explore if we can instead put a button in the tooltip with execution details which shows up on hover. This could solve both points above (if it has a "jump" icon it would be more discoverable, and in the future we could have more buttons). In that case the tooltip shown on hover might need to be more persistent.
I am not 100% sure if what I am proposing is the ideal solution but I believe it is worth exploring/waiting for some more feedback from other folks.
Uh oh!
There was an error while loading.Please reload this page.
Darshan808 commentedOct 24, 2024
@krassowski Would you suggest that I start exploring the idea of adding a "jump" button on hover, or would it be better to pause on this feature for now and gather more feedback before proceeding? |
krassowski commentedOct 24, 2024
I think either way is fine. Feedback takes time to accumulate organically, if you are interested in getting this done I would suggest pursuing it actively by sharing sscreenshots/recordings of what you can get working with least amount of effort (and worry about the code quality later) - you can open a topic on discourse or join a call to get more eyes on it. If it is not a high priority thing for you I would personally wait a bit. |
JasonWeill commentedDec 3, 2024
I just tried this code, and found an error:
importtimetime.sleep(100) |
jtpio commentedAug 22, 2025
Nice, thanks for working on this! Wondering if this feature could then be expanded (not necessarily in this PR) to also address: |
Darshan808 commentedOct 12, 2025
Just got back to working on this PR after a while. Made some updates (and edited the PR description above). Would love feedback! |
| // Auto-enable recordTiming if jump button is enabled | ||
| if(displayOptions.showJumpToCell){ | ||
| constrecordTiming=newSettings.get('recordTiming') |
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.
Why is this needed?
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 why:
jupyterlab/packages/notebook/src/actions.tsx
Lines 1883 to 1892 in889d093
| /** | |
| * Go to the last cell that is run or current if it is running. | |
| * | |
| * Note: This requires execution timing to be toggled on or this will have | |
| * no effect. | |
| * | |
| *@param notebook - The target notebook widget. | |
| */ | |
| exportfunctionselectLastRunCell(notebook:Notebook):void{ | |
| letlatestTime:Date|null=null; |
krassowski left a comment
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.
I think this makes sense. It is opt-in so should not cause much of an issue. The only think I would suggest is to make the description clearer.
I am also not sure if we should use "jump" or "scroll" in UI.
Uh oh!
There was an error while loading.Please reload this page.
krassowski left a comment
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.
One more thing, we don't usebtn in public CSS class names, lets keep it explicit.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Darshan808 commentedOct 28, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
|
99d9789 intojupyterlab:mainUh oh!
There was an error while loading.Please reload this page.
| font-size:var(--jp-ui-font-size1); | ||
| border:1px solidvar(--jp-border-color2); | ||
| color:var(--jp-ui-font-color0); | ||
| transition: all0.1s ease; |
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.
| transition: all 0.1s ease; |
This causes a slight delay in the disappearance of "Jump to cell" when the indicator loses hover:
Screencast.from.2025-12-12.13-29-47.mp4
Without transition:
Uh oh!
There was an error while loading.Please reload this page.
Fixes#16867
Description
Adds an optional button in the execution indicator tooltip that allows users to quickly navigate to the currently executing cell or the last executed cell.
Changes
showJumpToRecentExecutionButtonsetting to notebook extension (default:false)User facing changes
The button appears in the hover tooltip only when enabled and after at least one cell has been executed.