-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Steam menus disappear when the mouse is hovered over #924
Comments
My guess is this is related to #761 (I think steam uses electron). Fvwm has currently chosen to not create work around for this behavior, even though other wms have. I don't know the details well enough to know what workaround fvwm would need to deal with these behaviors of menus from chromium/electron apps. |
Of course, if I switch steam to unmanaged (Style steam Unmanaged) the issue is gone. So, by common sense, if
Then fvwm can have a solution eg. a reworked logic, not a quasi workaround. |
I noticed that when the menu disappears, the output of the
After doing some debugging, I found that removing these two lines stopped the menu from disappearing Line 2401 in 1d1c257
Line 2413 in 1d1c257
|
fvwm 2.6.x seems to behave the same, so it might be an old problem. |
this is definitely an issue in 2.6x. I've had this for a long time now; menus are broken in steam, and on some websites in various browsers. Possibly also related: there is a problem in getting the 'cast' menu to show up in chrome/chromium (i think i put in an issue about it before at some stage). edit: here is a (potentially-related) issue with getting the 'cast' menu to show up in chrome/chromium: |
See the title of the bug (impacted menu entries are placed into window's title (?), i.e. "Steam", "View", "Friends", etc.).
When you click on a menu entry, try to hover over the menu and the menu disappears.
Under different wms steam works fine (pekwm, icewm, openbox).
As I recon this was bug intro'd this year (2023), however, I haven't put any effort into identifying which commit causes this yet
The issue also exists with the default config file.
The text was updated successfully, but these errors were encountered: