You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new notebook in VS Code Insiders (doesn't have to be a Jupyter notebook).
Create and run a code cell that produces a lot of output. For example, in a Jupyter notebook connected to a Python kernel, run a code cell with the following code:
foriinrange(50):
print("test")
Cell output fills all vertical space, making it difficult to navigate the notebook. There doesn't seem to be a setting to limit the height and enable a scrollbar on the output itself.
Additional context: a Jupyter extension user just opted out of the native notebooks interface because there wasn't a way to limit the cell output height. Our extension supported a jupyter.enableScrollingForCellOutputs setting for our existing webview implementation of notebooks to address this user need, and users currently don't have a way to achieve the same thing in native notebooks. This is how the same code output is handled in our existing webview implementation:
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered:
Originally reported by @tobiasharren in microsoft/vscode-jupyter#5629
Steps to Reproduce:
Additional context: a Jupyter extension user just opted out of the native notebooks interface because there wasn't a way to limit the cell output height. Our extension supported a

jupyter.enableScrollingForCellOutputs
setting for our existing webview implementation of notebooks to address this user need, and users currently don't have a way to achieve the same thing in native notebooks. This is how the same code output is handled in our existing webview implementation:Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: