fix(startup): Firefox no longer hangs on "Heating up" after login (#303) #366
Merged
jared
merged 1 commits from 2026-10-16 22:36:53 -04:00
fix/firefox-persist-hang into lotus
No Reviewers
Labels
Clear labels
a11y
area: appearance
area: auth-session
area: build-ci
area: calls
area: desktop
area: media
area: messaging
area: mobile
area: moderation
area: navigation
area: notifications
area: settings
area: threads
bug
dependencies
docs
duplicate
enhancement
help wanted
invalid
needs-human-review
performance
planning
priority: critical
priority: high
priority: low
priority: medium
qa
question
research
security
tech-debt
ux
wontfix
Accessibility: keyboard, screen reader, contrast, motion
Client area: appearance
Client area: auth-session
Client area: build-ci
Client area: calls
Client area: desktop
Client area: media
Client area: messaging
Client area: mobile
Client area: moderation
Client area: navigation
Client area: notifications
Client area: settings
Client area: threads
Something is not working
Third-party package versions and advisories
README / LOTUS_* docs wrong or missing
This issue or pull request already exists
New feature
Need some help
Something is wrong
Re-render storms, leaks, heavy work on hot paths
Data loss, security hole, or crash on a main path
Broken feature or serious usability problem
Minor issue or polish
Wrong behaviour in an edge case or notable degradation
Manual QA: shipped, needs a human in a real environment
More information is needed
XSS, unsafe URLs, data leaks, auth/session
Code health, dead code, fragile patterns
Usability or visual inconsistency
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: LotusGuild/cinny#366
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #303.
initClientawaitednavigator.storage.persist()before creating the client. Chromium and WebKit answer it at once, but Firefox shows a permission prompt and leaves the promise pending until it's answered. So the app sat on "Heating up" (no sync, no crypto, no IndexedDB) for every Firefox user who didn't notice the prompt.Change: the request is still made, which is all the key-store protection (KE-1) needs, but startup waits at most 1.5 s for the answer. The comment claiming
persist()never prompts is corrected.Verified in Playwright Firefox with the prompt left unanswered (
persist()still pending):Not added: a Firefox project in the CI e2e suite, which the issue suggested. CI only installs Chromium and WebKit, and adding Firefox would lengthen every PR run. That can be a separate change if wanted.
tscclean · unit tests pass · ESLint clean (one existing warning elsewhere in the file).🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5