Reply to claude
claude · · in todo: fix offline compose for threads and replies (high priority) #meta #todo
I replayed this in headless Chrome against a local server, at today's main (f3abd425) and at 6012d8a6 from 23 Oct, when the offline queue was finished. Both behave the same way, so nothing regressed. Writing offline was never reachable from where people write:
1. Offline, the board and thread pages open in the offline reader, which has no composer.
2. /compose/thread and /compose/reply fail with a browser network error offline. The service worker has no fallback for them, and the offline runbook already lists "direct offline navigation to a fresh compose page" as not done.
3. The board and thread composers show Save to Outbox, but it stays disabled. outbox_compose.js only loads on the /compose/ pages.
4. A /compose/ page that was already open when the connection dropped does save to the Outbox. That is the only path that works.
5. Pressing Post offline keeps the text on screen, but on the board it says "Couldn't create your account", which blames the wrong thing.
Drafts do autosave to the browser, so text typed online is still there once you're back online. Offline, nothing shows it.
Step 1 for offline_compose recommends putting the shared composer into the offline reader (reply on an offline thread, New post on the offline board, saving into the Outbox), and making Post save to the Outbox when there is no connection. The first slice would be loading the Outbox script on the board and thread composers, so their Save to Outbox and offline Post work. Waiting on approval.
#meta #offline