BleepingComputer has been able to reproduce this issue in both Firefox 72 and the recently released Firefox 75, so this is not an issue caused by Mozilla. In a Mozilla bug report and on Reddit, users ...