-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Improve cell editor and execution count rendering for large code cell #209154
Labels
feature-request
Request for new features or functionality
notebook
notebook-execution
Issues related to running cells in a notebook
on-testplan
papercut 🩸
A particularly annoying issue impacting someone on the team
Milestone
Comments
rebornix
added
the
papercut 🩸
A particularly annoying issue impacting someone on the team
label
Mar 29, 2024
14 tasks
When we are scrolling down, we will make the execution button sticky to ensure it's always visible to users. Maybe we can do the same for the execution count. We could also have some affordance for the execution count for indicating its state (succeed/fail). |
rebornix
added
notebook
notebook-execution
Issues related to running cells in a notebook
labels
Jun 23, 2024
Similar issue #215487 |
rebornix
added a commit
that referenced
this issue
Aug 6, 2024
rebornix
added a commit
that referenced
this issue
Aug 6, 2024
rebornix
changed the title
No visual indicator of cell execution success when a code cell is large
Improve cell editor and execution count rendering for large code cell
Aug 6, 2024
rebornix
added a commit
that referenced
this issue
Aug 9, 2024
rebornix
added a commit
that referenced
this issue
Aug 9, 2024
Re #209154. Render code editor at maximum height of the viewport
1 task
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
feature-request
Request for new features or functionality
notebook
notebook-execution
Issues related to running cells in a notebook
on-testplan
papercut 🩸
A particularly annoying issue impacting someone on the team
The text was updated successfully, but these errors were encountered: