1780518 - Can't comment/react on linkedin when logged in with a google account

Status: RESOLVED WORKSFORME

(Web Compatibility :: Site Reports, defect)

Description

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Attachment: issue

Found in

• Firefox 102.1esr

Affected versions

• Firefox 102.1esr
• Firefox 103.0b8
• Nightly 104.0a1

Affected platforms

• Ubuntu 22.04
• macOS 12
• Windows 10

Steps to reproduce

1. Launch Firefox and go to https://www.linkedin.com/.
2. Log in using a google account.
3. LIke a post/react to one of the posts in the newsfeed.
4. Write a comment on one of the posts in the newsfeed.

Expected result

• The comment is posted and the react/like is saved and displayed.

Actual result

• The comment is not posted and the react/like is not saved/displayed.

Regression range

• Will look for one ASAP.

Additional notes
This is reproducible in Chrome. If the users logs in with a linkedin registered account, this issue is not reproducible. Suspecting this is a Chrome issue, but it can impact users on Fx who use it as a main browser but login on certain websites with their google account.

Comment 1

[Rainer Meier]

Perhaps it's related to this issue:
I am unable to sign-in to Thingiverse using my Google account in Firefox 103.0.

I already had problems previously using custom privacy settings and blocking all third party cookies, but it worked up and including to Firefox 102.0.1 using either standard cookie privacy settings or "cross-site tracking cookies, and isolate other cross-site cookies" setting.
Since version 103.0 I am completely unable to log on to my Thingiverse account. And yes, it still works with any other browser.

Comment 2

[Ciprian Georgiu, Desktop QA]

I've investigated this issue a bit, in order to find out if it was something that regressed in Firefox. As stated in comment 1, this is indeed a bug that occurs in Chrome as well, and on older Firefox builds (e.g. 78.0a1 Nightly, 2020-05-22). I've managed to reproduced the bug with a Gmail account logged into Linkedin with Win 10 x64.

Removing the regressionwindow-wanted keyword based on the above.

Comment 3

[Raul Bucata]

We appreciate your report. I was not able to reproduce the issue following the steps to reproduce:

https://prnt.sc/JqGw6f4X0HNi

Oana, is the issue still reproducible for you on the latest Nightly build?

Suggestion: Try clearing cache/data/cookies, disabling add-ons and Ad-blocker (if available) and extensions or use a clean profile, and check again? If there are any changes made to the default settings of the browser (e.g. in about:config) please revert to the default settings and try again. Also, have the required cookies been accepted for this page?

Tested with:

Browser / Version: Firefox Nightly 111.0a1 (2023-01-25) (64-bit)
Operating System: Windows 10 PRO x64

Comment 4

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Hello,
I can still reproduce on latest Nightly with a new profile. I managed to reproduce this issue with a Google account that has an OTP(2 step verification) set up on that account.

Comment 5

[Raul Bucata]

Thanks for the update, Oana. Does the issue reproduce with the same steps in Chrome as well? I am still unable to reproduce the issue, even with a google account that has 2FA enabled: https://prnt.sc/ytOJtF0Zu6ed

Tested with:

Browser / Version: Firefox Nightly 111.0a1 (2023-01-30) (64-bit)
Operating System: Windows 10 PRO x64

Comment 6

[Raul Bucata]

Dennis, after further investigations, it seems that the issue reproduces on Chrome as well. I was not able to reproduce it, as I am not prompted with the 2FA process, even if my test account has the 2FA enabled (both Linkedin and Google), but Oana can reproduce the issue on Chrome as well. Is there anything we can since the issue reproduces on Chrome, or should we move the issue to the relevant component?

Comment 7

[Calin Tanase]

Verified this issue and could not reproduce it on Firefox versions 122 and 124.

If the reporter can confirm that the issue reproduces in a new profile, we will gladly re-open the issue.

Environment:
Operating system: Windows 10
Firefox version: Nightly 124.0a1 (2024-01-24) / Release 122

Comment 8

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Confirming that I cannot reproduce this issue anymore on Firefox Nightly 124.0a1 nor Firefox 122.0(Release).

Comment 9

[Calin Tanase]

Thanks for looking into it.