Wrong background makes equation preview invisible #945

Activity

1. memeplex

   added

   bugSomething isn't workingSomething isn't working

   on Apr 1, 2026
2. memeplex

   changed the title [-]Wrong background makes equation preview unvisible[/-] [+]Wrong background makes equation preview invisible[/+] on Apr 1, 2026
3. juliasilge

   added

   vscode

   on Apr 1, 2026
4. memeplex commented on Apr 1, 2026

   

   memeplex

   on Apr 1, 2026

   Author

   More actions

   Perhaps it's not a recent change in VSCode but that I was using a non default theme until recently.

   Anyway the issue is that with "window.autoDetectColorScheme": true VSCode will only set "workbench.preferredLightColorTheme" and "workbench.preferredDarkColorTheme", or even remove them altogether when set to their defaults. Instead "workbench.colorTheme" is always set when "window.autoDetectColorScheme": false and then the equation preview uses the right foreground.
5. memeplex commented on Apr 1, 2026

   

   memeplex

   on Apr 1, 2026

   Last edited by memeplex

   Author

   More actions

   The issue may be here:

         const settings = configManager.getSettings();
         if (settings.computedThemeKind !== undefined) {
           return settings.computedThemeKind;
         }
         else {
           return settings.workbench.colorTheme.includes("Light") ? "light" : "dark";
         }

   while the right API seems to be vscode.window.activeColorTheme.kind (api link).
6. kv9898 commented on Apr 25, 2026

   

   kv9898

   on Apr 25, 2026

   Contributor

   More actions

   @memeplex my last PR (#864) already suggested using this api:

   quarto/apps/vscode/src/lsp/client.ts

   Lines 159 to 164 in 5f420f8

   	const sendThemeNotification = () => {
   	if (client) {
   	const kind = (window.activeColorTheme.kind === ColorThemeKind.Light || window.activeColorTheme.kind === ColorThemeKind.HighContrastLight) ? "light" : "dark";
   	client.sendNotification("quarto/didChangeActiveColorTheme", { kind });
   	}
   	};

   it's more likely that the notification was not "caught" by the receiver - I added a time delay in my initial version but it was later removed.