1772514 - Users are not able to open WhatsApp Web in Private WIndow

Status: RESOLVED DUPLICATE of bug 1767407

(Firefox :: Untriaged, defect)

Description

[abhinavsecondary]

Firefox for Android

Steps to reproduce:

Steps to reproduce:--

1. Open Firefox private window
2. Go to web.whatsapp.com
3. You will notice that page is continuously generating a request on https://web.whatsapp.com/?logout_reason=0 and unable to get the page that is required for login on WhatsApp web

I have verified this same behavior on Linux, Windows and on mobile also.

Impact:--
As you know Meta has largest social media users base and WhatsApp is a part of it.
Many users use private tab to login there WhatsApp when they are accessing there chats on somebodies else PC to maintain there privacy that if they directly close the private window then nobody can access there chats even if they didn't logout.
Due to this bug user are unable to access the login page of WhatsApp in a private window and this can create a wrong impression against Firefox in users mind and give an advantage to other browser to attract users to use there browser instead of Firefox

Actual results:

Web page continuously try to reload itself.

Expected results:

It should be get user to a web page where user are able to scan the QR code and able to access there messages

Comment 1

[abhinavsecondary]

I have found this issue in all Firefox(Linux/Windows/Android). So can you kindly change the device to all not only with just android.

And I forget to attach POC video.
Here is the POC video link -- https://drive.google.com/file/d/1yz4VRiNhxMOoWfsN7AYApI7Wr0Dp1fVp/view?usp=sharing

Thanks and Regards
Abhinav

Comment 2

[Andrew McCreight [:mccr8]]

This isn't really a security issue with Firefox itself, so I'm going to unhide this so that more people can see this to increase the chance that it is addressed.

Comment 3

[Andrew McCreight [:mccr8]]

I saw the same loop as described in comment 0, so I'm confirming this.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 5

[abhinavsecondary]

But It need to be fixed as it is valid issue?

Comment 6

[Peter Magyari (Desktop QA)]

I believe this is a duplicate of Bug 1767407.