This PR proposes changing the default scroll behavior in the extension to match the independent code and output scrolling behavior to None/Do Not Scroll as from these scroll options PR #193126. This change will enhance usability, especially for users managing large outputs or errors.
Rationale:
Improved Navigation and Debugging:
Large outputs or error messages often make it difficult to verify code execution quickly. Independent scrolling allows users to review outputs while keeping code in view, improving the debugging process and navigation.
Better Usability for Large Text and Errors:
For users with larger text settings or long error messages, independent scrolling reduces the need for excessive navigation, making it easier to focus on both code and output.
Familiar UX:
The independent scroll behavior aligns with the Jupyter notebook default, that has been widely tested . Keeping code and output scrollable separately reduces friction and creates consistency for users familiar with Jupyter’s default environment.
Proposal:
After reviewing these improvements, we propose setting the default scroll behavior to "None/Do not scroll." This removes the need for scrolling, keeping outputs fully visible without extra interaction. It smooths the transition for users familiar with Jupyter and is the likely the optimal choice for most users.
Description:
This PR proposes changing the default scroll behavior in the extension to match the independent code and output scrolling behavior to None/Do Not Scroll as from these scroll options PR #193126. This change will enhance usability, especially for users managing large outputs or errors.
Rationale:
Improved Navigation and Debugging:
Large outputs or error messages often make it difficult to verify code execution quickly. Independent scrolling allows users to review outputs while keeping code in view, improving the debugging process and navigation.
Better Usability for Large Text and Errors:
For users with larger text settings or long error messages, independent scrolling reduces the need for excessive navigation, making it easier to focus on both code and output.
Familiar UX:
The independent scroll behavior aligns with the Jupyter notebook default, that has been widely tested . Keeping code and output scrollable separately reduces friction and creates consistency for users familiar with Jupyter’s default environment.
Proposal:
After reviewing these improvements, we propose setting the default scroll behavior to "None/Do not scroll." This removes the need for scrolling, keeping outputs fully visible without extra interaction. It smooths the transition for users familiar with Jupyter and is the likely the optimal choice for most users.