Keep cursor at the previous position after cell split #10884
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
krassowski
force-pushed
the
keep-cursor-on-cell-split
branch
from
e2be668
to
a497ba3
Compare
|
@meeseeksdev please backport to 3.1.x |
meeseeksmachine
pushed a commit
to meeseeksmachine/jupyterlab
that referenced
this pull request
Aug 22, 2021
blink1073
pushed a commit
that referenced
this pull request
Aug 23, 2021
…plit (#10888) Co-authored-by: Michał Krassowski <5832902+krassowski@users.noreply.github.com>
github-actions
bot
added
the
status:resolved-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References
Fixes #10760
Code changes
Removes the cursor position change introduced in #10297. Also, fixes the docstring.
User-facing changes
Restores the behaviour as in JupyterLab 3.0:
With the current (undesirable behaviour) being:
Backwards-incompatible changes
None