Visual Studio Code released version 1.80, which brings the following new things:
Accessibility improvements
Accessible View Accessible View
New command "Open Accessible View" (Alt+F2) allows screen reader users to inspect content character by character, line by line. This method is called when hovering or when the chat panel responds to focus.
Accessibility Help Improve
New command "Open Accessibility Help" (Alt+F1) opens a help menu based on the current context. It currently works with editors, terminals, notebooks, chat panels, and inline chat.
Accessibility for notebooks
Added new accessibility help menu for notebooks to provide information on editor layout and notebook navigation and interaction.
Chat Audio Prompts
The GitHub Copilot chat experience now has audio cues, which can be enabled via audioCues.chatRequestSent , audioCues.chatResponsePending and audioCues.chatResponseReceived .
Settings editor text improvements
The introduction to the Settings editor (accessible via the Preferences: Open Settings (UI) command) is less verbose when navigating with a screen reader. The setting scope switcher now announces the actual name of the scope rather than the file path, and the setting description text has been cleaned up to not contain the original Markdown formatting.
workbench
Autoplay and loop preview videos
Video autoplay and looping can now be enabled for built-in video file previews. The relevant settings are:
mediaPreview.video.autoPlay— Enable video autoplay. Autoplaying videos are automatically muted.mediaPreview.video.loop— Enable video looping.
These settings are turned off by default.
Default file dialog location
New settings files.dialog.defaultPathto configure the default location where file dialogs (such as when opening or saving a file or folder) should appear when they are opened. This default is only used as a fallback when no other location is known, such as in an empty VS Code window.
Disable maximized editor group on tab double click
New setting workbench.editor.doubleClickTabToToggleEditorGroupSizesdisables switching the editor group size from maximized to restored when double-clicking the editor group's tab.
Controls the minimum width of fixed-width tabs
When workbench.editor.tabSizing set fixed to , the new setting workbench.editor.tabSizingFixedMinWidth controls the minimum size of tabs.
Editor group split size changed to "auto"
workbench.editor.splitSizing The new value set (called auto ) is the new default. In this mode, splitting an editor group will distribute the available size evenly to all editor groups only if no editor group has been resized. Otherwise, the space that split the editor group is split in half and placed in a new editor group.
Search for .gitignore exclusion behavior
When search.useIgnoreFiles set true to , the workspace's will now be honored regardless of whether the workspace was initialized as a Git repository .gitignore .
comment max height
Sets comments.maxHeight the maximum height limit that allows comments to be disabled, such as the height limit displayed for pull requests when using the GitHub Pull Request and Issues extension.
Troubleshoot issues in VS Code
There is a new command Help: Solve Problems in the Command Palette to help with problems in VS Code. The launched workflow helps identify the cause of an issue using special troubleshooting profiles and VS Code's extended bisection capabilities.
Disable Chromium sandbox
There are now two new settings to make it easier when you need to disable the Chromium sandbox:
- New command line option
--disable-chromium-sandboxto disable Chromium sandboxing for all processes in the application. - To permanently disable the Chromium sandbox at startup: Open the command palette (Ctrl+Shift+P), run the Preferences: Configure runtime parameters command, open the argv.json file to configure the runtime parameters, add "disable -chromium-sandbox": true , restart VS Code.
terminal
Image support Image support
Images in Terminal (previewed in the previous release) are now enabled by default. Images in the terminal usually work by encoding image pixel data into text, which is written to the terminal via special escape sequences. The currently supported protocol is the inline image protocol pioneered by Sixel and iTerm.
To test images manually, sample files can be downloaded from the libsixel repository :cat .six
Or use the imgcat python package or the imgcat script with .png, .gif or .jpg files:
This feature can be disabled via settings:
"terminal.integrated.enableImages": falseRemote tunnel link to WSL
The ability to connect to WSL via remote tunneling is now stable. If you are running Remote Tunnel on a Windows computer with WSL installed, you can choose to connect to WSL directly from Remote Explorer.
test
Terminal output support Terminal output support
Previously, test output shown in the Test Results view was always displayed in an embedded text editor, stripped of the rich styling, such as colors, styles, and symbols, that it might have had when run in a terminal.
This version displays output in a real xterm.js terminal.
The Test Results view is now fully functional, and the command to "Show Test Output" has been redirected to open the Test Results view instead of creating a temporary terminal.
The above is part of the content of version 1.80, and the complete update content can be found in the release announcement .