I wish these extensions could integrate with Firefox containers. Work and schools can easily ask people to use new sites which can not avoid and in that case it's best to defer to later day or just not fight with extensions.
That's kinda the full issue in standardizing. Gnome wants dbus for everything while sway wants wayland extension most things as they avoid using dbus code. So stuff like xsettings/xrdb or screensharing replacement has basically has wayland extension and a dbus API.
I hope some pseudo open source components come under non profit with reduced Google control. So other big player have bigger say in stuff Chromium and Android.
Certain libs use dlopen() which needs dynamic linking. Mesa, Pam, Qt (static is possible but a lot of stuff will break), Glibc(static is possible but nsswitch.conf will break), Alsa. So most graphical apps will fail to be pure static(Prob possible but will hardware/config specific). So we need to tackle and provide alternatives to dlopen.
Well web browsers are to complex to maintain by part time Dev unless you have an upstream to rebase on or do not mind in implementing new stuff. You need at least 10 to 20 full time Devs at the minimum and that's if you libaries for all web APIs which clearly Firefox and Chrome are not doing. I wish there was a way to browser modular frankly.