Opening Interactive window breaks editor "sticky scrolling" functionality

[hookxs]

Applies To

• Notebooks (.ipynb files)
• Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

In recent VS code there is a "sticky scrolling" feature which can be turned on via "editor.experimental.stickyScroll.enabled": true and it's actually pretty cool:-) However, when Interactive window is opened (and possibly closed, doesn't matter) this feature stops working.

Steps:

• turn on sticky scrolling
• start vscode
• open some python file to check that sticky scrolling works
• open interactive window (and leave open or close, doesn't matter)
• go back to your python file and see that now the scrolling is normal as if "sticky" were turned off.

Possibly this might have the same underlying cause as microsoft/vscode-jupyter#10846 since symbols analysis somehow gets messed up?

VS Code Version

Version: 1.70.0 (user setup) Commit: da76f93 Date: 2022-08-04T04:38:16.462Z Electron: 18.3.5 Chromium: 100.0.4896.160 Node.js: 16.13.2 V8: 10.0.139.17-electron.0 OS: Windows_NT x64 10.0.22000

Jupyter Extension Version

v2022.7.1002181843

Jupyter logs

No response

Coding Language and Runtime Version

No response

Language Extension Version (if applicable)

No response

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

No response

[rebornix]

Not sure how an extension would affect sticky scroll in the core, moving to VS Code for now.

[alexdima]

Sticky scroll is just using the DocumentOutlineProvider. @rebornix Do you think the document outline provider might stop working correctly after following these steps?

[rebornix]

@alexdima that might be the reason, and I'm wondering if the language service stopped working properly once we have interactive window open.

[jrieken]

@hookxs Do you still see this?

[hookxs]

Hi, no, this has apparently been fixed with one of the latest vs code updates. Also some other related problems were fixed, eg microsoft/vscode-jupyter#10846, so possibly the underlying issue was the same. Thanks:-)

[jrieken]

Ok, thanks for catching up