mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-11 11:59:55 -05:00
[GH-ISSUE #7747] Show persistent UI indicator when SharedArrayBuffer is unsupported #100600
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#100600
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MatissJanis on GitHub (May 7, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7747
Problem
We show the SharedArrayBuffer warning in the app, but it is easy for users to circumvent it by clicking around it and accepting the danger. After that, we never show it again — leaving users with no visual indication that they are running in a degraded/unsupported state.
Proposal
Add a persistent visual UI element (with a tooltip on hover) that shows a danger icon for users whose environment does not support SharedArrayBuffer.
A reasonable place for this could be the header, next to the "sync" / "server status" buttons.
The exact visual UI/UX is up for discussion.
Goals
@MatissJanis commented on GitHub (May 7, 2026):
Why? As shown by the crypto.randomUUID bug that caused grief for a lot of users - many people simply circumvent the SharedArrayBuffer warning. Which is risky, but if the users decide to do this - we should not stand in the way (there are some legitimate scenarios where this is the only option).
However, we should warn these users that they are in a "dangerous" state. Hence this issue.
Anyone: feel free to implement it. I'll be happy to review.
(we do not assign issues; just send a PR and/or discuss the UI/UX here)
@youngcw commented on GitHub (May 7, 2026):
Maybe instead of talking about the SharedArrayBuffer in the warning we can just say that Actual needs https, and then say what could happen if its not used. I think most people have no idea what the SharedArrayBuffer is or has any reason to care. That could be in addition to the persistent warning.
@MatissJanis commented on GitHub (May 7, 2026):
Yeah, that makes sense. Updating the existing wording would also be quite nice to focus more on the degraded user experience and not the specific technical limitation.