Ixion
@koebelt there is at least one person who reported that this fix was necessary for them: https://github.com/illixion/vscode-vibrancy-continued/issues/52 There was also more discussion here about refactoring this fix: https://github.com/illixion/vscode-vibrancy-continued/issues/38
I've updated this issue to reflect the new challenges posed in VSCode 1.82.0 update, and it will be used to track any possible solutions. This currently affects everyone on Windows...
Made a VSCode feature request to add the WCO setting back: https://github.com/microsoft/vscode/issues/198766 If this is affecting you, feel free to go to that feature request and give it a 👍...
You can use the "Disable Vibrancy" action to disable the transparency effect. Unfortunately, I don't think that there's a quicker way to disable transparency as it's applied through a CSS...
This isn’t something that I’m personally interested in implementing as I use VSCode exclusively in dark mode, so don’t expect it to be implemented any time soon, but pull requests...
Implemented in PR #146 and available in version 1.1.30
As mentioned in https://github.com/illixion/vscode-vibrancy-continued/issues/37#issuecomment-1342787176, this is affected by a .monaco-workbench.fullscreen background-color setting. Need to ensure that this works properly on macOS and Windows before implementing it. Feel free to use...
Hey, I've noticed this too on my PC with an Nvidia GPU, you could try disabling GPU rendering for VSCode and seeing if that fixes this. Follow this instruction: https://stackoverflow.com/a/58762168
Partial fix added in v1.1.24 to prevent installation on ARM Windows. Possible workaround would be to use the x64 version of VSCode through a compatibility layer, though this is suboptimal....
Closing this PR due to inactivity, please re-open once your theme is adjusted and ready to be merged