Stuck in a loading loop after login on portal.roboshadow.com in Private mode
Categories
(Core :: Privacy: Anti-Tracking, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox111 | --- | affected |
People
(Reporter: ctanase, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
233.94 KB,
image/png
|
Details |
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:
- 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
- Login with your google account.
- Observe the behaviour.
Expected Behaviour:
Able to login, redirected to the account page.
Actual Behaviour:
Stuck in a loading loop after logging.
Notes:
- Screenshot provided
- Reproducible in Private regardless of the ETP status
- Not reproducible in normal mode regardless of the ETP status
- Same behaviour on Firefox Release
Updated•2 years ago
|
Comment 1•2 years ago
|
||
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).
Comment 2•2 years ago
|
||
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'.
Comment 3•2 years ago
|
||
Yes, I was also able to log in with dom.indexedDB.privateBrowsing.enabled
enabled. Yay!
Comment 4•2 years ago
|
||
that's great. Should we close the bug now?
Comment 5•2 years ago
|
||
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.
Description
•