Hello @fiacco and @amarok yes, we are aware of this. This was caused due to an error in the webkitGTK package update.
And we are working on fixing this and preparing a software update to correct this.
Besides what was already said about firefox-esr as an alternative browser.
If you are comfortable with terminal commands you can revert this “bad” update by running the command:
sudo apt install libwebkit2gtk-4.0-37/amber-phone libjavascriptcoregtk-4.0-18/amber-phone gir1.2-javascriptcoregtk-4.0/amber-phone gir1.2-webkit2-4.0/amber-phone
This will revert webkitgtk to the previous version, and then you can wait until we release that
update.