Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Can’t login whatsapp web after early April 2022 update

  • 2 Antworten
  • 0 haben dieses Problem
  • 11 Aufrufe
  • Letzte Antwort von kib28242

more options

I asked this issue before. https://discourse.mozilla.org/t/cant-login-whatsapp-web-after-early-april-2022-update/97589 It's still continuing.

Expansion: 新同文堂 facebook container ublock origin

I tested a fresh install of firefox. Still can’t get login with the privacy mode. But the normal mode works. When I adjust the settings checking “Do not keep history” and “Clear cookies and website data when closing firefox”. It returned. After a new installation process, I stoped when I checked “Do not keep history” I speculated that this the effect.

But no matter which browser I used, I save no browsing history records. Why only firefox got compatibility problem? Or did whatsapp work anything behind?

I asked this issue before. https://discourse.mozilla.org/t/cant-login-whatsapp-web-after-early-april-2022-update/97589 It's still continuing. Expansion: 新同文堂 facebook container ublock origin I tested a fresh install of firefox. Still can’t get login with the privacy mode. But the normal mode works. When I adjust the settings checking “Do not keep history” and “Clear cookies and website data when closing firefox”. It returned. After a new installation process, I stoped when I checked “Do not keep history” I speculated that this the effect. But no matter which browser I used, I save no browsing history records. Why only firefox got compatibility problem? Or did whatsapp work anything behind?

Alle Antworten (2)

more options

Go to about:config and change dom.cache.privateBrowsing.enabled to true. This will be default in version 122.

Hilfreich?

more options

zeroknight 提道

Go to about:config and change dom.cache.privateBrowsing.enabled to true. This will be default in version 122.

It's working fine in v122.0.1

Geändert am von kib28242

Hilfreich?

Stellen Sie eine Frage

Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.