Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Accessibility] Ctrl+M (editor.action.toggleTabFocusMode) does not work inside terminal input field #172024

Closed
jooyoungseo opened this issue Jan 23, 2023 · 3 comments · Fixed by #172395
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders terminal-input Relating to typing in the terminal not doing the right thing, IMEs not working, etc. verified Verification succeeded
Milestone

Comments

@jooyoungseo
Copy link

CC @meganrogge

Reproducible Steps

  1. Load screen reader.

  2. Open terminal.

  3. Focus in terminal input area.

  4. Press Ctrl+M to toggle tab-key move (editor.action.toggleTabFocusMode).

  • Notes: I don't hear any change. It does not seem to work.

Expected Behavior

Pressing Ctrl+M key needs to toggle the tab-key move mode.

System Info

Version: 1.75.0-insider (system setup)
Commit: f1b0923
Date: 2023-01-23T11:53:59.088Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes

@meganrogge meganrogge self-assigned this Jan 23, 2023
@meganrogge meganrogge added accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug labels Jan 23, 2023
@meganrogge meganrogge added this to the January 2023 milestone Jan 23, 2023
@meganrogge
Copy link
Contributor

Yep does not work on windows

@meganrogge meganrogge added windows VS Code on Windows issues terminal-input Relating to typing in the terminal not doing the right thing, IMEs not working, etc. and removed windows VS Code on Windows issues labels Jan 23, 2023
@meganrogge
Copy link
Contributor

the logs show that the keybinding works and Invoking command editor.action.toggleTabFocusMode. but then it doesn't happen

2023-01-25 06:25:58.152 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
2023-01-25 06:25:58.152 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
2023-01-25 06:25:58.153 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2023-01-25 06:25:58.301 [info] [KeybindingService]: / Soft dispatching keyboard event
2023-01-25 06:25:58.302 [info] [KeybindingService]: | Resolving ctrl+M
2023-01-25 06:25:58.304 [info] [KeybindingService]: \ From 1 keybinding entries, matched editor.action.toggleTabFocusMode, when: no when condition, source: built-in.
2023-01-25 06:25:58.306 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: KeyM, keyCode: 77, key: m
2023-01-25 06:25:58.306 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: KeyM, keyCode: 43 ('M')
2023-01-25 06:25:58.307 [info] [KeybindingService]: | Resolving ctrl+M
2023-01-25 06:25:58.307 [info] [KeybindingService]: \ From 1 keybinding entries, matched editor.action.toggleTabFocusMode, when: no when condition, source: built-in.
2023-01-25 06:25:58.308 [info] [KeybindingService]: + Invoking command editor.action.toggleTabFocusMode.
2023-01-25 06:25:58.447 [info] [KeybindingService]: / Soft dispatching keyboard event
2023-01-25 06:25:58.448 [info] [KeybindingService]: | Resolving ctrl+M
2023-01-25 06:25:58.449 [info] [KeybindingService]: \ From 1 keybinding entries, matched editor.action.toggleTabFocusMode, when: no when condition, source: built-in.

@meganrogge
Copy link
Contributor

it only gets run when there's an editor view model, which there isn't when the terminal is focused

export abstract class CoreEditorCommand<T> extends EditorCommand {
public runEditorCommand(accessor: ServicesAccessor | null, editor: ICodeEditor, args?: Partial<T> | null): void {
const viewModel = editor._getViewModel();
if (!viewModel) {
// the editor has no view => has no cursors
return;
}
this.runCoreEditorCommand(viewModel, args || {});
}
public abstract runCoreEditorCommand(viewModel: IViewModel, args: Partial<T>): void;
}

meganrogge added a commit that referenced this issue Jan 25, 2023
@VSCodeTriageBot VSCodeTriageBot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Jan 30, 2023
@jrieken jrieken added the verified Verification succeeded label Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders terminal-input Relating to typing in the terminal not doing the right thing, IMEs not working, etc. verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants