Text column edges

Outbox

Purpose: Keep what a person writes or likes on their own device until the server has accepted it, so losing the connection never loses work and nothing is published twice. Scenario: Offline, a member opens a saved thread (the offline reader, a proposed concept with no entry yet), clicks Reply and writes. Post says "Saved on this device, not sent", and the reply is listed under the thread with a dashed border. When the connection returns, the page sends it through the normal prepare, sign and finalize steps, keeping the prepared post so a retry after a lost response finalizes the same post. The reply appears in the thread once, and Tools → Outbox shows it as accepted with a link. Sources: item states (source unavailable), device storage (source unavailable), composer capture and queueing (source unavailable), delivery (source unavailable), Outbox page (source unavailable), offline compose pages (source unavailable), runbook, browser test (source unavailable). Limits: anonymous posts and images stay in the composer; a request that fails while the browser reports a connection is never queued automatically. Delivery holds a cross-tab lock, so only one tab sends at a time and a send cut off by a closed page is retried at once.