close open chat on esc #25

New issue

Closed

opened 2026-10-17 21:05:35 +00:00 by tlasol · 1 comment

tlasol commented

2026-10-17 21:05:35 +00:00

Member

there’s no way to close an open chat from the keyboard. in other messengers (telegram, whatsapp desktop) esc closes the current chat and leaves an empty placeholder on the right

the placeholder matters: some users close chats for privacy, so nobody can glance more than the roster, so this is an expected behaviour

expected:

with a chat open, pressing esc closes it
the right side shows the same empty state as the start screen
no chat is highlighted in the roster

actual:

esc does nothing, the chat stays open

notes:

if something is open on top of the chat (reply, search, popup, file preview), esc closes that first and the chat only on the next press
a draft in the input field should be kept after closing

there’s no way to close an open chat from the keyboard. in other messengers (telegram, whatsapp desktop) esc closes the current chat and leaves an empty placeholder on the right the placeholder matters: some users close chats for privacy, so nobody can glance more than the roster, so this is an expected behaviour expected: - with a chat open, pressing esc closes it - the right side shows the same empty state as the start screen - no chat is highlighted in the roster actual: - esc does nothing, the chat stays open notes: - if something is open on top of the chat (reply, search, popup, file preview), esc closes that first and the chat only on the next press - a draft in the input field should be kept after closing

tlasol added the

feature request

ui/ux

severity: medium

labels

2026-10-17 21:05:35 +00:00

ann referenced this issue from a commit

2026-10-18 10:26:07 +00:00

Esc closes the open chat (#25: "close open chat on esc"): the right side goes back to the start screen's empty pane and no row in the list is picked. It is the last of the window's Escape shortcuts (chat-actions.ts, after the one that leaves selection mode), so every Esc consumer that is already there keeps the key first: the overlays' document listener closes the menu, the dialog, the certificate question, the topmost sheet (Settings, the in-window XML console, the media viewer) and the shell's lower layers (the details panel, the add-account sheet) and marks the key handled, the fields that keep their own Esc stop it (the composer's banner and tray, the search bar, the list filters, the voice recorder), and the app lock still holds every shortcut back. The new handler then steps through what belongs to the chat itself before the chat: its search bar when open but not focused, a thread pane, an edit (the stashed words come back) or a reply waiting in the field, and only then Store.closeChat, the same path the phone's pane switch and Android's back gesture take, whose doc comment now names Esc. The draft stays in Drafts and draft-sync publishes it on the change of openChat exactly as on a switch to another chat; a key still composing in an input method is left alone. esc-close-chat.test.ts boots the shell on the mock and checks the empty pane and the cleared selection, the draft kept and sent through chatDraft, a menu, a sheet, the search bar, a reply and an edit each taking the first press, and a key already handled elsewhere left alone. The changelog's Unreleased section gets a Changed entry.

ann commented

2026-10-18 10:35:24 +00:00

Owner

Esc closes the open chat and leaves the empty pane, with no chat highlighted. Anything open over the chat closes first, one per press: a menu, dialog, sheet, search bar, thread, reply or edit. The draft is kept.

Fixed in 0.6.1: https://dev.another.im/another-im/anotherim-js/releases/tag/v0.6.1

ann closed this issue

2026-10-18 10:35:24 +00:00

ann referenced this issue from a commit

2026-10-25 23:34:41 +00:00

The events libtacky 1.1.3 sends typed (its #25: stickers <CreateProgress>, storage <MigrateProgress>, notify <MissedCall>, otr <State>, muc <Invite>, conn <AuthError>, calls <Active> and <Outgoing>, author <Changed>'s authors, which crossed as strings) are read as numbers and booleans: every consumer was looked at (state/stickers.ts and storage.ts take Number(), room-invites.ts and connectivity.ts accept true/1/'1' and read false and '0' as no, authors.ts takes the object, the Android shell's CallEvent.isTrue both shapes; MissedCall, otr <State> and calls <Active>'s since are read by nothing), and the one gap closed: calls <Outgoing>'s video now sets the outgoing call's video from its first event (bool(), true, 1 or '1'). The mock emits the typed shapes: <Outgoing> with video, <Active> with since in microseconds; its muc <Invite> and <MigrateProgress> were typed already. Tests: typed-events.test.ts (relink false after true clears the relink, old '1'/'0' too; request false is an invitation and true a request, '0' too; MigrateProgress numbers; Outgoing video true and false, Active with since).