Http3 has existed in ff for a while. What triggered this was some back end service switching to http3, triggering the bug.
Even if you don't update your browser, the world updates around it
Even if you don't update your browser, the world updates around it
> Telemetry has nothing to do with this, it just happens to be one of the first services with H3 load balancer.
If telemetry really had "nothing to do with" the bug, then the fact that telemetry "just happens to be one of the first services with H3 load balancer" wouldn't trigger the bug.
The question isn't whether "backend services" forms the conceptual essence of the problem - I think we all agree it doesn't.
The question is whether it "happens to be" triggered by backend services.