(In reply to Max Inden from comment #16) > Thank you for the additional logs via mail! > > Paraphrasing the above to make sure I understand correctly. On an _ARM_ machine running _Windows for ARM_ (Surface Pro 11) fosstodon.org does not load with aarch64, x86 and x86-64 Firefox Nightly builds with `network.http.http3.use_nspr_for_io` set to `false`. The latter two (x86, x86-64) are presumably run via _Windows for ARM_ emulation layer. Yes. > Do I understand correctly that all other H3 pages work fine, e.g. https://quic.nginx.org/ or https://cloudflare-quic.com/ ? I did not check others as I don't know who uses H3. https://quic.nginx.org/ shows "You're not using QUIC right now, but don't despair," with NSPR pref off, while it shows "Congratulations! You're connected over QUIC." with NSPR pref on. Tested with `mozregression --launch 2024-09-04 -a https://quic.nginx.org/ --pref network.http.http3.use_nspr_for_io:true`. Similar result on the cloudflare page. But as I showed to Kershaw, the test result is a bit flaky. Sometimes it connects well with QUIC (and then breaks on a few reload and then permanently stuck on HTTP2), or just goes straight to HTTP2 from the start.
Bug 1916558 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Max Inden from comment #16) > Thank you for the additional logs via mail! > > Paraphrasing the above to make sure I understand correctly. On an _ARM_ machine running _Windows for ARM_ (Surface Pro 11) fosstodon.org does not load with aarch64, x86 and x86-64 Firefox Nightly builds with `network.http.http3.use_nspr_for_io` set to `false`. The latter two (x86, x86-64) are presumably run via _Windows for ARM_ emulation layer. Yes. > Do I understand correctly that all other H3 pages work fine, e.g. https://quic.nginx.org/ or https://cloudflare-quic.com/ ? I did not check others as I don't know who uses H3. https://quic.nginx.org/ shows "You're not using QUIC right now, but don't despair," with NSPR pref off, while it shows "Congratulations! You're connected over QUIC." with NSPR pref on. Tested with `mozregression --launch 2024-09-04 -a https://quic.nginx.org/ --pref network.http.http3.use_nspr_for_io:true`. Similar result on the cloudflare page. But as I showed to Kershaw offline, the test result is a bit flaky. Sometimes it connects well with QUIC (and then breaks on a few reload and then permanently stuck on HTTP2), or just goes straight to HTTP2 from the start.
(In reply to Max Inden from comment #16) > Thank you for the additional logs via mail! > > Paraphrasing the above to make sure I understand correctly. On an _ARM_ machine running _Windows for ARM_ (Surface Pro 11) fosstodon.org does not load with aarch64, x86 and x86-64 Firefox Nightly builds with `network.http.http3.use_nspr_for_io` set to `false`. The latter two (x86, x86-64) are presumably run via _Windows for ARM_ emulation layer. Yes. > Do I understand correctly that all other H3 pages work fine, e.g. https://quic.nginx.org/ or https://cloudflare-quic.com/ ? I did not check others as I don't know who uses H3. https://quic.nginx.org/ shows "You're not using QUIC right now, but don't despair," with NSPR pref off, while it shows "Congratulations! You're connected over QUIC." with NSPR pref on. Tested with `mozregression --launch 2024-09-04 -a https://quic.nginx.org/ --pref network.http.http3.use_nspr_for_io:true`. Similar result on the cloudflare page. But as I showed to Kershaw offline, the test result is a bit flaky. Sometimes it connects well with QUIC (and then breaks on a few reload and then permanently stuck on HTTP2), or just goes straight to HTTP2 from the start. Edit: And with the nspr pref on, things work consistently without flakyness.