Threads 1b: a thread read as a chat #283
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom#283
Loading…
Reference in a new issue
No description provided.
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?
Part 1b of #242 (D-063). The design is on #242.
A thread read as a chat:
The direct-message chats should share this component (#265).
Tests: seed a long chain; e2e for grouping, the reply field and read-when-seen; screenshots.
Merged in #298; main run #487 green. Verified: e2e thread-chat.spec (order, one name per run, flat chains, fork indentation, subject only where it changes, unread marks, opening a message, replying from the field with Ctrl+Enter) in desktop/android/iphone; full e2e suite 344 passed on the branch; unit tests for the layout; lint with CI's three clippy commands; screenshots looked at on desktop and phone. Forks become chips and subject changes split off in #284.