Closed Bug 1813546 Opened 2 years ago Closed 2 years ago

Stuck in a loading loop after login on portal.roboshadow.com in Private mode

Categories

(Core :: Privacy: Anti-Tracking, defect, P3)

Firefox 111
Other
Android
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox111 --- affected

People

(Reporter: ctanase, Unassigned)

References

(Blocks 1 open bug, )

Details

Attachments

(1 file)

Attached image roboshadow.png

Environment:
Operating system: OnePlus 6 A6000 (Android 11) / Google Pixel 5 (Android 13)
Firefox version: Nightly 111.0a1-20230129090848 / Release 109.0-20230112150232

Preconditions:
• Private window opened

Steps to reproduce:

  1. Go to https://portal.roboshadow.com/login?utm_source=Phone_App&utm_medium=App_Ref&utm_campaign=Phone%20APP&utm_term=Portsl&utm_content=Phone_APP_PortalLink
  2. Login with your google account.
  3. Observe the behaviour.

Expected Behaviour:
Able to login, redirected to the account page.

Actual Behaviour:
Stuck in a loading loop after logging.

Notes:

  1. Screenshot provided
  2. Reproducible in Private regardless of the ETP status
  3. Not reproducible in normal mode regardless of the ETP status
  4. Same behaviour on Firefox Release
Flags: needinfo?(twisniewski)

They are using Firebase, which won't work in private browsing mode until indexedDB (and possibly other APIs) are fully supported in private browsing mode in Firefox in . WhatsApp Web runs into similar loading loops for similar reasons (bug 1767407).

Blocks: tp-firebase
No longer blocks: tp-breakage
Severity: -- → S3
Flags: needinfo?(twisniewski)

With our recent enhancements to support IndexedDB in private browsing mode, I was able to login using google account and go past the loading loop. Please note that since supporting IndexedDB in private browsing is still an under development feature; you have to toggle on the feature switch from about:config with the key 'dom.indexedDB.privateBrowsing.enabled'.

Yes, I was also able to log in with dom.indexedDB.privateBrowsing.enabled enabled. Yay!

that's great. Should we close the bug now?

Sure, since we're actively working on shipping this ASAP, let's close this bug with the caveat that it will work with that pref enabled until it's on by default for everyone.

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

Attachment

General

Creator:
Created:
Updated:
Size: