Cells render incomplete or overlapping when using cell movement
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
In a large Jupyter Notebook, when using cell movement (e.g. gg or G), cells do not render correctly.
When going to the top of the document, often lines of code in the cells are not visible.
When going to the bottom of the document, often cells are overlapping.
However, it is kind of non-deterministic, sometimes both artifacts appear.
As soon as one uses the mouse scroll or scroll bar, the artifact goes away.
To Reproduce
Steps to reproduce the behavior:
- Create: New Jupyter Notebook
- Create two cells with 10 lines and 20 cells (more if you have a large monitor) without content
- Use gg to go to the first cell
- Use G to go to the last cell
Expected behavior
I expect that cells and their contents render regularly independent on the movements that are performed.
Screenshots
Right after going to the first cell, only one line of the two cells are visible (they both have 10 lines).
Right after going to the last cell, there are overlapping cells visible (they are all empty).
Environment:
- Extension (VsCodeVim) version: 1.32.4
- VSCode version: 1.106 (VSCodium on Linux) and 1.07 (VS Code on Windows 10)
- OS: Arch Linux and Windows 10 (same problem on both machines)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in a large Jupyter Notebook with multiple multi-line cells, then use gg and G as described. Compare the rendering immediately after cell movement with the result after mouse or scrollbar scrolling. Done means cells and their contents render correctly without requiring additional scrolling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, typescript, vscode
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100