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

Cells running out of order after a copy and paste #15768

Open
jbwhit opened this issue Feb 7, 2024 · 5 comments
Open

Cells running out of order after a copy and paste #15768

jbwhit opened this issue Feb 7, 2024 · 5 comments
Labels
bug tag:Regression Behavior that had been broken, was fixed, and is broken again
Milestone

Comments

@jbwhit
Copy link

jbwhit commented Feb 7, 2024

Description

I used "C" and "V" to copy and paste two cells, and following that, the flow became broken around these cells. The cells were run "out of order" from their visual . Here is a screenshot of the notebook that I ran using + from the top down. You can see the out of order Input markers as the order that these cells were run.

Screenshot 2024-02-07 at 10 24 14 AM

But, it probably makes more sense to see what's happening in a video, so I have a video demonstrating what I see here: https://youtu.be/RRl8iqGzYag

Reproduce

I cannot reproduce this, and I've tried many different times. This has happened to me several times before, but I can't get it to reliably occur. I have this notebook still open for now, and can run diagnostics on this if it would be helpful to know something more from this session.

Expected behavior

I expect that the cells "know" their position in the webpage, and so what is next and previous corresponds exactly with the vertical position in the notebook.

Context

  • Operating System and version: Mac OS 14.3
  • Browser and version: Firefox 122.0 (64-bit)
  • JupyterLab version:
IPython          : 8.21.0
ipykernel        : 6.29.0
ipywidgets       : 8.0.4
jupyter_client   : 8.6.0
jupyter_core     : 5.7.1
jupyter_server   : 2.12.5
jupyterlab       : 4.1.0
nbclient         : 0.8.0
nbconvert        : 7.14.2
nbformat         : 5.9.2
notebook         : not installed
qtconsole        : not installed
traitlets        : 5.14.1
Browser Output Here's a screenshot of my Javascript console if that helps: Screenshot 2024-02-07 at 10 32 21 AM
@jbwhit jbwhit added the bug label Feb 7, 2024
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Feb 7, 2024
@krassowski krassowski added this to the 4.1.x milestone Feb 8, 2024
@krassowski krassowski added the tag:Regression Behavior that had been broken, was fixed, and is broken again label Feb 8, 2024
@krassowski
Copy link
Member

Thank you a lot for reporting @jbwhit! This could be the same issue as #15610. Do you have the full Notebook windowing mode enabled, or are you using the default defer?

@jbwhit
Copy link
Author

jbwhit commented Feb 8, 2024

Looks similar, do not use the full Notebook windowing mode as far as I can tell. I spent a couple of minutes trying to find documentation on that:

Screenshot 2024-02-08 at 9 54 42 AM

but I'm not aware of how to enable that option (or what it is, exactly).

@krassowski
Copy link
Member

@jbwhit

image

The documentation you are searching is cross-project. JupyterLab docs are on https://jupyterlab.readthedocs.io/

@jbwhit
Copy link
Author

jbwhit commented Feb 18, 2024

Thanks for the tip. I can confirm that I'm using the default defer and not using full.

@krassowski
Copy link
Member

@jbwhit I believe this should be fixed now. Can you test a 4.2.x version to confirm?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug tag:Regression Behavior that had been broken, was fixed, and is broken again
Projects
None yet
Development

No branches or pull requests

3 participants