4 ms·

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 browse

• jacquesm 5y ago
  My browser isn't supposed to have any 'backend services'. Especially not backend services that I did not explicitly opt in to.
  • semi-extrinsic 5y ago
    It's not a backend service on your browser, it's on whatever webpage you tried to visit.
    • foxfluff 5y ago
      This bug can be triggered without visiting any webpage at all.
    • torstenvl 5y ago
      No, it's in the browser. Turn off all data collection and the bug disappears. https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c10 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c10
      • progval 5y ago
        lower in the linked thread: > Telemetry has nothing to do with this, it just happens to be one of the first services with H3 load balancer.
        • torstenvl 5y ago
          You... do understand that that's self-contradictory, right? It's impossible for both parts of that sentence to be true. 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.
          • charcircuit 5y ago
            I think he means you that you couldn't eliminate the bug by disabling telemetry. It just will be triggered by something else later.
            • torstenvl 5y ago
              Sure. But the thread is in reply to this post: https://news.ycombinator.com/item?id=29918998 https://news.ycombinator.com/item?id=29918998 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.
    • jacquesm 5y ago
      I really don't get this comment after a whole thread full of good information on this.