Hides numeric counts on room and sidebar badges while keeping the dot
indicator active. Defaults to on. Exposed in both Appearance and
Cosmetics settings panels.
- getUnreadInfo: guard stale-count clamp with roomHaveUnread; exclude own messages
from clamp trigger; walk live timeline to compute real fallback counts using
PushProcessor instead of hard-coding dot badge
- roomToUnreadAtom: remove mDirectAtom dependency for DM parent filtering;
add ClientEvent.Room handler to seed badge state when rooms join
- sessionsHighlightAtom added to track highlight counts per inactive session
- AccountSwitcherTab: show UnreadBadge on inactive session rows and sidebar icon
- HandleNotificationClick moved outside ClientRoot loading gate so SW postMessages
are never dropped during account-switch reloads
- iOS Safari event.source=null guard removed; type-check used instead
- ToRoomEvent simplified: writes pendingNotificationAtom + sets active session,
delegates navigation to NotificationJumper
- NotificationJumper: jumpingRef prevents repeated navigation; stable performJumpRef
avoids re-registering listeners on every atom change during account switch
- BackgroundNotifications: uses SW showNotification for reliable tap routing on iOS;
dedupeId is now userId+eventId scoped; visibility guard prevents backgrounded
in-app popups; ref pattern avoids stale closure on settings
- SW: persist/restore notification settings across iOS SW restarts via Cache API;
group notifications by room (tag + renotify); prefer navigate() over postMessage
when available; prefer visible tab on notificationclick
- pushNotification: resolveSilent respects tweaks.sound; recipientId in title;
fallbackNotification removed (redundant)
- RoomTimeline: use ref for handleOpenEvent to stop re-pulling on every new message
typing `+:` in the message editor will bring up the emoticon
autocomplete prompt, where choosing an emoticon will clear the editor
and react with that emoticon under the latest message
this commit also splits the autocomplete prefixes in two: ones that can
be used anywhere in the message, and those that only work at the
beginning
also i set a default type param on one of the autocomplete query
functions because who wants to keep typing out that type everywhere all
the time
P500 resolves to 1.0 (fully opaque) so pending messages were not visually dimmed at all. Switch to Placeholder (0.5) for pending to match Discord's treatment, and P300 (0.75) for failed to keep it visually distinct from pending.
- Remove 'Sending...' text from pending messages; text is now dimmed via opacity while in-flight to reduce timeline jump
- Add 'Delete' button alongside 'Retry' on failed sends, using mx.cancelPendingEvent for client-side removal
- Clear the input box immediately on send rather than waiting for the network round-trip to complete