You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test the settings window.autoDetectColorScheme and window.autoDetectHighContrast. They now work on MacOS and in the Web as well.
On the web: High contrast detection is enabled on the latest Edge by default. On Chrome it has to be enabled with chrome://flags, enable Forced colors . light dark mode is enabled on Chrome by default, on Edge it has to be enabled in the Edge settings.
When window.autoDetectHighContrast is enabled (default on), VS Code reacts to high contrast change in the OS. When detected, it uses the theme specified at workbench.preferredHighContrastColorTheme.
When window.autoDetectColorScheme is enabled (default off), VS Code reacts to dark/light mode change in the OS. When detected, it uses the theme specified at workbench.preferredLightColorTheme and workbench.preferredDarkColorTheme
Test that VSCode detects the color scheme & hc changes
Test that VSCode switches to the preferred theme
Test that the workbench.colorTheme setting is changes to the new theme, but only in the user settings
Test that changes to the autoDetect settings to the preferred theme settings are honored.
Test that when toggling the the autoDetect settings back to off, the theme that was used before is set again. (Note: the last used theme is not remembered across restarts of VSCode)
Test that when starting VSCode, any color scheme OS changes that happend while VSCode was closed are detected
Test that changing the current theme to a non preferred theme is honored and is only changed back to the preferred theme when there is an actual color scheme OS change detected.
The text was updated successfully, but these errors were encountered:
I saw some weird behaviour with restoring the previous configured theme. I was editing my settings (in the file) and removed all of them, including the "window.autoDetectColorScheme": true one. When I saved, my previous theme came back into the settings file. I wonder if we can be more clever and not do this if I change the settings file myself.
Ubuntu 20.04 supports light/dark mode. Electron detects the scheme on startup, but has a bug that the update event is not working: electron/electron#23861 (comment)
So in VS Code, "window.autoDetectColorScheme": true works on Linux, but only on startup.
Refs: #105715
Complexity: 3
Create Issue
Test the settings
window.autoDetectColorScheme
andwindow.autoDetectHighContrast
. They now work on MacOS and in the Web as well.On the web: High contrast detection is enabled on the latest Edge by default. On Chrome it has to be enabled with
chrome://flags
, enableForced colors
. light dark mode is enabled on Chrome by default, on Edge it has to be enabled in the Edge settings.When
window.autoDetectHighContrast
is enabled (default on), VS Code reacts to high contrast change in the OS. When detected, it uses the theme specified atworkbench.preferredHighContrastColorTheme
.When
window.autoDetectColorScheme
is enabled (default off), VS Code reacts to dark/light mode change in the OS. When detected, it uses the theme specified atworkbench.preferredLightColorTheme
andworkbench.preferredDarkColorTheme
workbench.colorTheme
setting is changes to the new theme, but only in the user settingsThe text was updated successfully, but these errors were encountered: