Fixes/workarounds for Steam client menus/flickering #886
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A fix, a tool for workarounds, and a workaround:
X.H.EwmhDesktops: Fix menus in Steam client
More specifically, ignore
ClientMessageEvent
s for unmanaged windows. Steam likes to send_NET_ACTIVE_WINDOW
requests for all its windows, including override-redirect ones, which used to result in an invocation ofwindows
with a no-op Endo—equivalent to a call torefresh
. But this refresh makes Steam close its menus immediately.Fixes: ValveSoftware/steam-for-linux#9376
Fixes: xmonad/xmonad#451
X.H.FloatConfigureReq: New module to customize ConfigureRequest handling
Implements a replacement event handler for
ConfigureRequestEvent
to work around misbehaving client applications such as Steam, rxvt-unicode and others that try to restore their absolute window positions. Primarily motivated by the Steam client being almost completely unusable in xmonad lately.(I've been running this code in my xmonad.hs for other purposes for years.)
X.H.FloatConfigureReq: Add fixSteamFlicker
For ease of use, provide
fixSteamFlicker
as a pre-packagedfloatConfReqHook
that can easily be added directly to ahandleEventHook
.Also, for discoverability, re-export it from X.U.Hacks.
Checklist
I've read CONTRIBUTING.md
I've considered how to best test these changes (property, unit, manually, ...) and concluded:
been running the
X.H.FloatConfigureReq
stuff for years locally; the rest is fresh and ideally needs to be manually tested by some folksI updated the
CHANGES.md
file