https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255128
--- Comment #15 from Felix Palmen <[email protected]> --- (In reply to Craig Leres from comment #12) > basically if XGetWMHints() doesn't return hints create synthetic hints. Unfortunately, this doesn't change anything. Added this minimal change to fvwm3 1.0.2 code: --- fvwm/add_window.c.orig 2021-05-06 22:48:59 UTC +++ fvwm/add_window.c @@ -1873,6 +1873,16 @@ void setup_window_name(FvwmWindow *fw) void setup_wm_hints(FvwmWindow *fw) { fw->wmhints = XGetWMHints(dpy, FW_W(fw)); + if (!fw->wmhints) + { + fw->wmhints = XAllocWMHints(); + if (fw->wmhints) + { + fw->wmhints->flags = InputHint | StateHint; + fw->wmhints->input = True; + fw->wmhints->initial_state = NormalState; + } + } set_focus_model(fw); return; with no luck. Are you sure THIS works in your patched wm? > Example: Top navigation on www.freebsd.org. E.g. hover on "Documentation", > move down to "Handbook", click. The menu will just close. Would really be great to find out why chromium recently has a problem with fvwm… -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "[email protected]"
