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

When background is transparent, highlighted text not inverted #962

Closed
npezza93 opened this issue Sep 10, 2017 · 5 comments
Closed

When background is transparent, highlighted text not inverted #962

npezza93 opened this issue Sep 10, 2017 · 5 comments
Assignees

Comments

@npezza93
Copy link
Contributor

npezza93 commented Sep 10, 2017

In ZSH when you tab complete, you can tab through options. When you set xterms background to transparent(say you are on a dark background) the text color does not get inverted correctly on the v3 branch. Changing the foreground, cursor, or selection colors did not fix the issue.

Repro steps:

  • Set xterms theme background to transparent
  • jump into zsh
  • tab complete a command

If that doesn't really make sense I've attached a gif to help to show what I'm talking about.
xterm

@Tyriar
Copy link
Member

Tyriar commented Sep 10, 2017

Transparent is no longer a valid background color. This is related to #936, previously black was just used as the default background color which breaks when the background is not black.

Did you call this to get into this state?

var term = new Terminal({
  theme: {
    background: 'transparent'
  }
});

@Tyriar Tyriar self-assigned this Sep 10, 2017
@npezza93
Copy link
Contributor Author

@Tyriar Yes, that is what I called to get into that state.

@npezza93
Copy link
Contributor Author

Changing the background to 'none', yields the desired results and inverts the text color correctly. Closing.

@corwin-of-amber
Copy link

With #1236, transparent background is allowed. But text highlighted with "inverse video" is still rendered incorrectly (invisible text over white background).

@corwin-of-amber
Copy link

I take that back – this was fixed in 4.3.0!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants