vscode: Cmd+1/2 doesn't focus on the input box of Interactive Window

Environment data

VS Code version: 1.56.0
Jupyter Extension version (available under the Extensions sidebar): v2021.6.832593372
Python Extension version (available under the Extensions sidebar): v2021.5.842923320
OS (Windows | Mac | Linux distro) and version: Mac 11.2.3 (20D91)
Python and/or Anaconda version: Python 3.7.10, conda 4.9.2
Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
Jupyter server running: Local

Expected behaviour

Focus should return to input box after Ctrl+2.

Actual behaviour

Focus does not return to input box.

Steps to reproduce:

Open vscode
Open an Interactive Window in the second pane (cmd+ shift + p -> “Jupyter: Create Interactive Window”)
Toggle between cmd+1 and cmd+2

GIF of issue

vscode_bug

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

Every time I switch to the Interactive Window, this log appears

```Info 2021-05-25 19:27:54: Attempting to start a server because of preload conditions ... ```

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 13
Comments: 24 (10 by maintainers)

Most upvoted comments

Not to “me too”, but this bug is nigh debilitating, particularly for keyboard-only users. It annoys me all day every day. I eagerly await any fixes or workarounds.

+13

daanzu on May 27, 2021

I’m having the same issue with VSCode version 1.57.1 Python extension version 2021.6.944021595 on Windows 10 Pro.

Jumping between group focuses using ctrl+(1/2/3) won’t put the cursor into the interactive window execution cell. I’m a bit surprised to see such a lengthy and well-documented case for this issue and no resolutions available.

natephysics on Jul 6, 2021

Getting this same issue on WSL running VSCode version 1.56 and Python extension version v2021.6.944021595.

Switching to interactive window via keyboard shortcut does not focus within the interactive window itself, just the top level tab.

Tabbing once the interactive window is in focus (from a hotkey switch) will tab to other editor groups instead of within the window.

If you click on the interactive window with the mouse, tab will then move between components within the window as expected. From here, after 5 or 6 tabs you can get to the input box.

This is a pretty cumbersome bug as far as workflow effect. If there’s anything I can help look at or clarify from this side please let me know. Thanks!

Scaleframe on Jun 17, 2021

Yes the TextAreaFocusTracker does not receive focus when using CMD+1/CMD+2. It does if I click in the webview, but not when using the keyboard.

rchiodo on Jun 7, 2021