You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some preliminary testing suggests that the change in yshui/picom@79fc36b with regard to the _NET_WM_CLIENT_OPACITY (see yshui/picom#134 for a discussion why) has introduced a race condition where the updated opacity value is actually one state behind (i.e. focused for unfocused windows and !focused for focused ones).
I suggest continuing the discussion in the upstream issue.
Platform: Arch 5.4.14 amd64
Drivers: mesa, xf86-video-intel
WM: i3-gaps
Compton version: vgit-e0149 (picom-tryone latest)
Compton configuration: https://pastebin.com/AaHv0vp5
Steps of reproduction
In opacity-rule, the programs are considered focused when they are not, and considered not focused when they are.
Therefore, I gave higher opacity to non focused programs, and lower opacity to focused programs.
Expected behavior
Focused programs should be focused, and non focused programs shouldn't. When using compton before, I didn't face this problem.
Current Behavior & Other details
I use --experimental-backend, but the issue exists also without the flag.
The text was updated successfully, but these errors were encountered: