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

workbench.colorCustomization.editor.background does not respect transparency #134213

Closed
rowanG077 opened this issue Sep 30, 2021 · 5 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@rowanG077
Copy link

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.60.2
  • OS Version: NixOS unstable

Steps to Reproduce:

  1. Add workbench.colorCustomization.editor.background to the settings.json and set it to some color which has transparency. For example #ff000059.
  2. The editor does NOT show any transparency.

Expected behaviour:
The editor pane should be transparent according the workbench.colorCustomization.editor.background setting. This probably extends to most color options.

@rowanG077
Copy link
Author

In fact there used to be a pr for this: #52707

But it got closed for no apparent reason.

@alexdima
Copy link
Member

alexdima commented Sep 30, 2021

I think this is about having the window be transparent. (i.e. seeing the desktop background through the vscode window and through the code editor).

@rowanG077
Copy link
Author

rowanG077 commented Sep 30, 2021

@alexdima Yes this is what I expected to happen if I added transparency to the background. For example my terminal can set a background color with transparency which means the content is still solid while the background in the terminal is transparent and any windows/background below the terminal are visible.

@bpasero
Copy link
Member

bpasero commented Oct 1, 2021

/duplicate #32257

@github-actions github-actions bot locked and limited conversation to collaborators Nov 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants
@bpasero @alexdima @rowanG077 and others