Skip to content
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

cell created in wrong location (above VS below, and vic.) #16148

Closed
ggrrll opened this issue Apr 11, 2024 · 5 comments
Closed

cell created in wrong location (above VS below, and vic.) #16148

ggrrll opened this issue Apr 11, 2024 · 5 comments
Labels
bug status:Needs Info status:Needs Triage Applied to new issues that need triage

Comments

@ggrrll
Copy link

ggrrll commented Apr 11, 2024

Description

when creating a new cell above cell 'x' (below) , sometimes it does the opposite, creating it below (above) , both with key. shortcut and click on cell-toolbar button
(and when moving with arrows, it skips the reference cell 'x')

Context

console errors

I have many errors, here are a couple -- not sure if relevant

image

thanks!

@ggrrll ggrrll added the bug label Apr 11, 2024
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Apr 11, 2024
@krassowski
Copy link
Member

I think this may have been fixed as a side effect of && widget !== this._willBeRemoved) addition in #16013.

Would you be able to test the latest 4.2.0 beta?

@ggrrll
Copy link
Author

ggrrll commented Apr 11, 2024

thanks
it's a bit difficult, as we work with a specific env, which we do not update often ...anyway, looking forward to see that fix in the main release :)

@FoSuCloud
Copy link
Contributor

@ggrrll Can you provide a reproduction video?
I did not find this problem in version 4.2.0b1

@JasonWeill
Copy link
Contributor

@ggrrll Could you please provide a video if you can still reproduce this? If you could try with a 4.2.0 beta version, that would help as well. I appreciate your help!

@ggrrll
Copy link
Author

ggrrll commented Apr 16, 2024

Hi,

sorry, busy days a work -- don't worry, if you understood the problem and you fixed it in the new v., then I will see it at some point (I will have to push the new v. internally, in our working env.)

Thanks for your contribution!

@ggrrll ggrrll closed this as completed Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug status:Needs Info status:Needs Triage Applied to new issues that need triage
Projects
None yet
Development

No branches or pull requests

4 participants