On Wed, Feb 1, 2023 at 7:02 AM Julian Smith <[email protected]> wrote: > > On Tue, 31 Jan 2023 18:05:50 -0500 > Morgan Aldridge <[email protected]> wrote: > > > Running `xprop` on a Firefox window with the OpenBSD homepage loaded > > confirms my suspicions: > > > > WM_NAME(STRING) = "Mozilla Firefox" > > _NET_WM_NAME(UTF8_STRING) = "OpenBSD — Mozilla Firefox" > > > > So, I'd suggest submitting a bug report upstream w/Firefox. (I believe > > the Firefox codebase is used for Thunderbird, as well, so I suspect > > this issue affects it too.) > > Many thanks for this. I get the same results with xprop. > > I had a look for WM_NAME and there's already a Firefox bug for this: > https://bugzilla.mozilla.org/show_bug.cgi?id=1679182.
Good find. > One of the comments mentions a suggested workaround is to set > LC_ALL=en_US.UTF-8, and this fixes the problem for me: > > LC_ALL=en_US.UTF-8 firefox > > (I think https://www.openbsd.org/faq/faq10.html implies that > `en_US.UTF-8` is supported on OpenBSD, but any suggestions about a > better workaround would be welcome.) It turns out that during a recent migration to new workstation workstation hardware, I introduced a typo in setting `LC_CTYPE=en_US.UTF-8` in my ~/.xsession, so my locale was not actually being set. Fortunately, that seems to have benefited both of us. > More generally, it looks like the problem is caused by Firefox > changing around version 0.83 to using a non-ascii dash in its titlebar > text. > > It uses `gtk_window_set_title()` to set the titlebar. I guess the > implication is that GTK is not setting WM_NAME if the text is not pure > ascii and the locale is not utf8. It looks like gtk2 is obsolete > though, so i haven't submitted a bug report. This makes sense and is probably a reasonable implementation, but I'll look into it a bit deeper. GTK+ 2 is indeed obsolete, but I'm now curious whether GTK+ 3 handles it any better. > BTW i tried fvwm3 but it doesn't appear to behave differently from > fvwm2 here. Good to know. Thanks, Morgan Aldridge
