Closed Bug 1668897 Opened 5 years ago Closed 5 years ago

Cannot load messages in Google Voice with http3.enabled

Categories

(Core :: Networking: HTTP, defect, P2)

Product:
Core
Component:
Networking: HTTP
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox-esr78 --- unaffected
firefox81 --- unaffected
firefox82 --- unaffected
firefox83 --- wontfix

People

(Reporter: yoasif, Assigned: dragana)

References

(Regression,
URL
)

Details

(Keywords: nightly-community, regression, Whiteboard: [necko-triaged])

Steps to reproduce:

  1. Navigate to https://voice.google.com/u/0/messages as a logged in user

Expected result:

I see my Google Voice messages and can send messages.

What happens:

Never ending spinner from page.

Setting network.http.http3.enabled back to false resolves the issue.

84:01.35 INFO: No more integration revisions, bisection finished.
84:01.35 INFO: Last good revision: adf38a6442cf89e88135dbf0b2d3b53c07a9d800
84:01.35 INFO: First bad revision: 459f586ec85a54f60d475d8315db21ba43de742e
84:01.35 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=adf38a6442cf89e88135dbf0b2d3b53c07a9d800&tochange=459f586ec85a54f60d475d8315db21ba43de742e

URL: https://voice.google.com/u/0/messages
Has Regression Range: --- → yes
Has STR: --- → yes
Keywords: nightly-community
Regressed by: 1668019
Summary: Cannot load messages in Google Voice → Cannot load messages in Google Voice with http3.enabled
Assignee: nobody → dd.mozilla
Status: NEW → ASSIGNED
Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged]

Set release status flags based on info from the regressing bug 1668019

status-firefox81: --- → unaffected
status-firefox82: --- → unaffected
status-firefox-esr78: --- → unaffected

I cannot

Blocks: 1653178

There was 2 bugs that have been fix in last 10 day that could have probably caused this issue.
May I ask you to retest it. Thank you!

Flags: needinfo?(yoasif)

It works for me now. Oddly, mozregression says that Bug 1651882 fixes it. The builds starting from 2020-10-06 fixes it, in any case.

Flags: needinfo?(yoasif)

Therewas 2 bug I have fixed somewhere around that time that have probably fixed the issue.
Thank you for retesting.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.