The browser's implementation of HTTP3 appears to be the root of the problem. While there isn't a permanent fix from Mozilla for the bug, there is a workaround that will help in some cases.