Open noahboegli opened 4 years ago
Is the window rendered correctly when frame-opacity = 1;
is set?
Can you please post the output of xprop _NET_FRAME_EXTENTS
for that window?
Setting frame-opacity = 1;
fixes the issue. I must have missed in the docs. Sorry for the useless issue.
Thank you !
@noahboegli still looks like a bug either in picom or in i3, can you do this:
Can you please post the output of
xprop _NET_FRAME_EXTENTS
for that window?
That will be helpful.
still looks like a bug either in picom or in i3
Window and window-frame dimensions seem to be handled differently by some window managers. See https://github.com/yshui/picom/issues/413#issuecomment-674458787 for a different issue with geometry / frame-dimensions.
Of course, here is the output: _NET_FRAME_EXTENTS(CARDINAL) = 2, 2, 20, 2
Cheers
Yep, looks like our bug...
Noticed the same here, setting frame-opacity=1
"solved" it. Although I'm using AwesomeWM, not i3. It happens to me in any fullscreen application, be it Firefox, VLC or even xterm/Alacritty, just as if they had a top bar, but they don't. Here's the output of xprop _NET_FRAME_EXTENTS
for any fullscreen window: _NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 23, 0
. It looks a bit different, so I guess the culprit here is my WM?
@Mark42XLII
so I guess the culprit here is my WM?
Yes.
This is a "bug" in i3. It seems to affect applications that request window decoration dimensions via the _NET_REQUEST_FRAME_EXTENTS
message — like awk, mpv, and most Java applications.
According to the spec, the wm should then update the _NET_WM_FRAME_EXTENTS
property with "estimates" of the window decoration dimensions. This becomes a problem as i3 usually doesn't bother setting/updating _NET_WM_FRAME_EXTENTS
(probably not really conforming to the spec), leaving said windows in a state where the property most likely doesn't reflect the actual dimensions of its decoration — at least not in the way we expect. (See the commit that added that feature to i3)
Due to the specific way i3 handles its decorations — i.e. not in the reparent-frame like (all?) other reparenting wms — even if the window actually has decorations with the dimensions set in _NET_FRAME_EXTENTS
, picom would require a hack to handle frame-opacity
on the i3-frame window like expected. I'd consider frame-opacity
to be incompatible with i3 by desing — at least for now.
Platform
Arch on kernel 5.9.10
GPU, drivers, and screen setup
Nvidia GTX1070, nvidia proprietary driver 455.45.01-2
Environment
i3
picom version
vgit-dac85
Configuration:
Steps of reproduction
Expected behavior
The dark gray rectangle is not there.
Current Behavior
The dark gray rectangle creates a transparency zone.
Stack trace
n/a