Timed room mute silently overwrites a manual notification-mode change made during the mute window #21
Closed
opened 2026-09-12 01:50:54 -04:00 by jared
·
0 comments
No Branch/Tag Specified
lotus
update-packages
sw-fix
read-me-update
image-path-changes
dm-calls
fix-2469
renovate/element-hq-element-call-embedded-0.x
renovate/npm-i18next-http-backend-vulnerability
renovate/npm-vite-vulnerability
dev
docs-update
more-theme
fix-257
imporve-thread-reply
revert-2402-improve-menu-congestion
mxidColor-toggle
update-sw-main-msg
v4.11.1
v4.10.5
v4.10.4
v4.10.3
v4.10.2
v4.10.1
v4.10.0
v4.9.1
v4.9.0
v4.8.1
v4.8.0
v4.7.1
v4.7.0
v4.6.0
v4.5.1
v4.5.0
v4.4.0
v4.3.2
v4.3.0
v4.2.3
v4.2.2
v4.2.1
v4.2.0
v4.1.0
v4.0.3
v4.0.0
v3.2.0
v3.1.0
v3.0.0
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.8.2
v1.8.1
v1.8.0
v1.7.0
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.0
v1.3.2
v1.3.1
v1.3.0
v1.2.1
v1.2.0
v1.1.0
v1.0.0
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
Milestone
No items
No Milestone
Audit 2026-09 · High
Projects
Clear projects
No projects
Notifications
Due Date
Dependencies
No dependencies set.
Reference: LotusGuild/cinny#21
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.
Severity: high · Type: bug · Confidence: high
Location:
src/app/features/room-nav/RoomNavItem.tsx:299-316(unmuteRoom,scheduleMuteTimer),src/app/pages/client/ClientNonUIFeatures.tsx:299-328(MuteTimerRestore)Problem
unmuteRoom(mx, roomId)unconditionally callssetRoomNotificationPreference(mx, roomId, RoomNotificationMode.Unset, RoomNotificationMode.Mute)when a timed mute expires — it never re-checks whether the room's notification mode is stillMuteat that point. If the user manually changes the notification mode (e.g. to "All messages" via the bell icon/RoomNotificationModeSwitcher) while a timed mute is still pending (either in the same tab, another tab, or after a reload whereMuteTimerRestorere-arms the stale timer fromlocalStorage), the previously scheduled timer still fires later and silently reverts their explicit choice back toUnset, with no toast or indication of what happened.How to trigger
Mute a room for 15 minutes. Before the 15 minutes elapse, manually switch the room's notification mode to "All messages" via the notification switcher. Wait past the original mute duration — the mode silently reverts to default/unset.
Suggested fix
Before restoring, check the room's current notification mode and only reset it if it is still
RoomNotificationMode.Mute(compare against live state, not the closed-overprevMode); otherwise just drop the stale timer entry.Filed from the September 2026 client audit (branch
lotus@4bea4895).