Just for completeness, I think this was: https://bugzilla.mozilla.org/show_bug.cgi?id=1777895 and should be fixed with FF 104+ (the described workaround solved it for me on FF 103)