-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Unrendered last cell and warning in the search function (3.1.0b1) #10578
Comments
Thx for reporting @krassowski. Can you detail a little bit the scenario driving to that issue? Are you seeing a un-rendered cell before working in the last cell? |
I will fill in the details once I find a way to reproduce. |
I encountered more suspicious behaviour related to cell rendering. Let's start by creating some cells:
Now, I delete the empty cells I created and follow to add new cells with Shift + Enter again: this causes one of the cells to become unrendered. We can recover it by cut-paste operation: I also encountered it in an earlier trial without the extra step of removing cells I think: |
@krassowski I will look into the detailed report. You have at hand the scenario that fails, so if you could apply them on jupyterlab 2.3, this would help me to nail down the origin. Did we have some of those issue in 2.3 and didn't see them, or is it on master? |
There might be an interaction with undo function as well. |
Did a few test on master (2.3 seems to behave the same) and I would say there is a special case of the last cell (there seems to be a explicit scrolling somewhere). Will look at fixes tomorrow. |
@krassowski I have opened a fix in #10602. The reported issue are solved, and I have not been able to reproduce a unrendered cell. However, please try out the fix, you may have more ideas to break it 👍 |
Fixed by #10602 |
Description
There are no logs in developer console.
Reproduce
TBD
Expected behavior
Context
Previous similar issue reported in #10435 and deemed fixed with #10505 (which certainly improved things).
CC @echarles @goanpeca
The text was updated successfully, but these errors were encountered: