Change:
private _revealInViewWithMinimalScrolling(viewIndex: number, firstLine?: boolean) { const firstIndex = this.view.firstVisibleIndex; <del> if (viewIndex <= firstIndex) { </del> <ins> const elementHeight = this.view.elementHeight(viewIndex); if (viewIndex <= firstIndex || elementHeight >= this.view.renderHeight) { </ins> this._revealInternal(viewIndex, true, CellRevealPosition.Top, firstLine); } else { this._revealInternal(viewIndex, true, CellRevealPosition.Bottom, firstLine);

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes Executing current (1) cell with Shift-Enter jumps/scrolls to the end of the output section of next (2) cell. This causes problems if the next cell has an output already that is very long (eg. graphs). You have to scroll back a lot unnecessarily. The screen will jumpt to the end of the output of the next (2) cell. It should ideally jump to the code part of the next (2) cell, showing the code on the middle of the screen, allowing to see the end of the output of the just executed (1) cell. Current behaviour is a bit illogical and also you have to scroll back to see the results of the cell you just ran. See Video: <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --Version: 1.81.0 (system setup) Commit: Date: 2023-08-02T12:37:13.485Z Electron: 22.3.18 ElectronBuildId: Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.

Steps to Reproduce: Have one cell with any code a cell below that outputs lots of output, more than a screen worth of results the cell (1) with shift-Enter
duplicate of
re-opening since this behavior will still exist for and could be improved
I'm unable to get the next cell to scroll completely Here's my notebook document along with the output <details<summaryipynb file</summary</detailsScroll setting has been set to When shift+executing the second cell (which has 40 lines), I expect the 3rd cell to be displayed towards the middel or at least stay at the bottom, so that I can see the output from the second cell (as thats' what i just ran) I would expect there to be enough scrolling to display the next cell as well ass the output of the previous cell I.e. display the next cell towards the middle As you can see from the screen recording, the previous cell is still running (blue progress bar on the top) However the 3rd cell is taking up all of the realestate Actually you can replicate this even when running the first cell (shift+ enter). There no way to see the previous output except change the scroll setting to I would expect there to be no scrolling at all, as the first line in the next cell (in fact full input cell) is visible
please feel free to create a new issue and close this if its unrelated.
- I'm not sure I follow, but you mentioned a screen recording. Can you create a new issue with that? This issue is also for the default
verification: in settings (default) two cells with the code both cells so they have output the viewport so that one output takes up the whole view by itself the first cell with shift+enter that the input of the second cell (which should now be focused) is fully visible