As updating devel/glib20 opens a pandemonium let's revert a few changes.
Tested via www/firefox on X11 and Wayland.
Created attachment 215338 [details]
I have 3.24.18 in the gnome@ devel repo, which also includes devel/glib20 update to 2.64. Been dogfooding this combination for over a month now. The glib update is not only necessary to update GNOME eventually, but certain other non-GNOME software in ports also need newer glib, namely MATE.
Glib update requires skipping several minor versions and touches platform-specific code. In case of regressions fixes maybe non-trivial.
Gtk update lacks both risks. I don't use Gnome or any other DE, so my motivation is to get bug fixes and Wayland improvements.
(In reply to Charlie Li from comment #2)
> certain other non-GNOME software in ports also need newer glib
Even one of my ports, see x11/wofi/files/patch-glib-2.56.
Also, Glib update requires switching to Meson because upstream stopped generating configure, config.h.in, Makefile.in, etc. since 2.57 then removed autotools support in 2.59.
Exp-run looks fine
A commit references this bug:
Date: Thu Jun 18 00:56:16 UTC 2020
New revision: 539511
x11-toolkits/gtk30: update to 3.24.20
Exp-run by: antoine