Open Bug 1774211 Opened 2 years ago Updated 2 years ago

"Start now" button in Gmail Workspace pop-up doesn't work

Categories

(Core :: Networking, defect, P2)

Firefox 101
defect

Tracking

()

UNCONFIRMED

People

(Reporter: dimitrijevicmaj, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(5 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:101.0) Gecko/20100101 Firefox/101.0

Steps to reproduce:

Open Gmail, go to Meet, "New meeting", "Start now".

Actual results:

Pop-up closes, nothing happens.

Expected results:

Google Meet should open in new tab or window and a meeting should start.

I didn't manage to reproduce this issue on the latest versions Nightly 103.0a1 and Firefox 101.0.1.
Could you please retest this using Firefox in Troubleshoot Mode and with a new profile to eliminate custom settings as a possible cause?

http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Flags: needinfo?(dimitrijevicmaj)

(In reply to Ina Popescu from comment #1)

I didn't manage to reproduce this issue on the latest versions Nightly 103.0a1 and Firefox 101.0.1.
Could you please retest this using Firefox in Troubleshoot Mode and with a new profile to eliminate custom settings as a possible cause?

http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

The problem still occurred when I tried reproducing the issue in Troubleshoot Mode while still using my default profile.
However, simply switching to a new profile fixed the issue, therefore there was no need to run the browser in Troubleshoot Mode.

Which of my settings is then preventing Gmail from running Meet in a new tab?

Flags: needinfo?(dimitrijevicmaj)

(In reply to dimitrijevicmaj from comment #2)

(In reply to Ina Popescu from comment #1)

I didn't manage to reproduce this issue on the latest versions Nightly 103.0a1 and Firefox 101.0.1.
Could you please retest this using Firefox in Troubleshoot Mode and with a new profile to eliminate custom settings as a possible cause?

http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

The problem still occurred when I tried reproducing the issue in Troubleshoot Mode while still using my default profile.
However, simply switching to a new profile fixed the issue, therefore there was no need to run the browser in Troubleshoot Mode.

Which of my settings is then preventing Gmail from running Meet in a new tab?

Could you go to about:support, click on "Copy text to clipboard", and attach it to this bug?
Setting this to NEW to have developer's opinion on this. If this is not the right component, please move it to a more appropriate one. Thanks.

Component: Untriaged → WebRTC
Product: Firefox → Core
Attached file Application Basics.txt

(In reply to Ina Popescu from comment #3)

(In reply to dimitrijevicmaj from comment #2)

(In reply to Ina Popescu from comment #1)

I didn't manage to reproduce this issue on the latest versions Nightly 103.0a1 and Firefox 101.0.1.
Could you please retest this using Firefox in Troubleshoot Mode and with a new profile to eliminate custom settings as a possible cause?

http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

The problem still occurred when I tried reproducing the issue in Troubleshoot Mode while still using my default profile.
However, simply switching to a new profile fixed the issue, therefore there was no need to run the browser in Troubleshoot Mode.

Which of my settings is then preventing Gmail from running Meet in a new tab?

Could you go to about:support, click on "Copy text to clipboard", and attach it to this bug?
Setting this to NEW to have developer's opinion on this. If this is not the right component, please move it to a more appropriate one. Thanks.

Attached a new Text Document titled Application Basics that contains the copied text from about:support.

The severity field is not set for this bug.
:mjf, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mfroman)

I do not see anything obvious in the attachment in comment 4. We might be able to learn more if we could see the JS console output. A copy about:webrtc could also shed some light on this (I suspect that no RTCPeerConnection is being created, but it would be good to know for sure).

Flags: needinfo?(mfroman) → needinfo?(dimitrijevicmaj)
Attached file aboutWebrtc.html
Flags: needinfo?(dimitrijevicmaj)

I'm not able to reproduce either.

Dimitrij, before doing the repro steps, could you hit CTRL + SHIFT+ j to open the Multiprocess Browser Console, and hit the 🗑 button to clear it?

Then, after doing the repro steps shown in your video, do you see any differences in that output if you compare it to doing the same in a clean profile?

Flags: needinfo?(dimitrijevicmaj)

(In reply to Jan-Ivar Bruaroey [:jib] (needinfo? me) from comment #9)

I'm not able to reproduce either.

Dimitrij, before doing the repro steps, could you hit CTRL + SHIFT+ j to open the Multiprocess Browser Console, and hit the 🗑 button to clear it?

Then, after doing the repro steps shown in your video, do you see any differences in that output if you compare it to doing the same in a clean profile?

I do see a difference in the two outputs. Please find attached two screenshots of the two different outputs as seen in the Multiprocess Browser Console, '0' being the output of the browser launched in a clean profile and Troubleshoot Mode.

Flags: needinfo?(dimitrijevicmaj)
Attached image 1
Attached image Zero

Looks to me like gmail is hitting lots more CSP violations in the profile that is not functioning. The about:webrtc in comment 8 shows that no RTCPeerConnection was ever created. This is not a webrtc problem.

Component: WebRTC → Networking

Hi Reporter,

Could you try to capture a http log?
I'd like to see if there is any networking request fails. Note that the log may contain some privacy information (e.g., cookies), so please send it to necko@mozilla.com directly.

Thanks.

Flags: needinfo?(dimitrijevicmaj)

(In reply to Kershaw Chang [:kershaw] from comment #14)

Hi Reporter,

Could you try to capture a http log?
I'd like to see if there is any networking request fails. Note that the log may contain some privacy information (e.g., cookies), so please send it to necko@mozilla.com directly.

Thanks.

Hi,

I've captured a http log and have sent it to the email address you provided.

Flags: needinfo?(dimitrijevicmaj)

Thanks for the log.
It shows some requests were cancelled, but we don't know why.

Severity: -- → S3
Priority: -- → P2
See Also: → 1760580
Whiteboard: [necko-triaged]
a11y-review: requested → ---
Flags: behind-pref-

(In reply to Kershaw Chang [:kershaw] from comment #16)

Thanks for the log.
It shows some requests were cancelled, but we don't know why.

Even after playing around with various settings on and off, several updates and trying to logically find the root cause I still cannot find what is stopping this from working normally.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: