putt1ck Neat workaround, can confirm issue still present with latest FF (127.0.2) and workaround still resolves issue.
