alacritty: Background opacity doesn't work is full screen mode or nvim
background opacity doesn’t work…
- in full screen mode
- in nvim in tmux via remote host
System
OS: Windows Version: 5
Logs
[2020-08-03 14:41:50.536691500] [DEBUG] Estimated DPR: 1.25
[2020-08-03 14:41:50.536691500] [DEBUG] Estimated Cell Size: 8 x 15
[2020-08-03 14:41:50.536691500] [DEBUG] Estimated Dimensions: None
[2020-08-03 14:41:50.652691000] [INFO] Device pixel ratio: 1.25
[2020-08-03 14:41:50.683965400] [INFO] Initializing glyph cache...
[2020-08-03 14:41:50.700655300] [INFO] ... finished initializing glyph cache in 0.0248494s
[2020-08-03 14:41:50.717148300] [INFO] Cell Size: 8 x 15
[2020-08-03 14:41:50.717148300] [INFO] Padding: 0 x 0
[2020-08-03 14:41:50.717148300] [INFO] Width: 1024, Height: 768
[2020-08-03 14:41:50.752981600] [INFO] PTY dimensions: Line(51) x Column(128)
[2020-08-03 14:41:50.768586600] [INFO] Using ConPTY backend
[2020-08-03 14:41:50.768586600] [INFO] Initialisation complete
[2020-08-03 14:41:50.768586600] [DEBUG] Term::resize dimensions unchanged
[2020-08-03 14:41:50.768586600] [INFO] Width: 1024, Height: 768
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 1
- Comments: 16 (5 by maintainers)
That’s how wayland works by design. Fullscreen windows can’t be transparent.
That doesn’t bring any value here, the only thing that is not working as expected is Fullscreen opacity. nvim behavior is correct and intended. We won’t change the way it’s being handled now to completely incorrect behavior you want (by make transparent every content on a screen).
There’s not point to make truecolored text transparent, that’s not how it works, so we’re handling everything correctly here. Only background should be transparent, not the entire window contents.
I’m clearly saying that WINDOWS can disable it to gain better performance and that could be related to a fullscreen mode we’re using and us being a GPU accelerated program. In fullscreen WINDOWS can disable compositor for OpenGL apps for them to gain lower input latency, especially knowing that you’ve mentioned a flicker in other issue, which could signal a composition being disabled.
I feel like it’s related to #4072. The opacity is being disabled by Windows here, and I guess it’s for a reason, like direct scan out or we’re using a fullscreen mode that prevents compositor from taking place in fullscreen, and so the composition is being bypassed resulting in a missing transparency.
If you’re using truecolor or setting background color to some value, it won’t work by design.
You’d likely need something like that in neovim config.