Reply to guest
guest · · in Bug roundup: published drafts remain in the composer
Bug roundup: published drafts remain in the composer (PF-20261030-B03)
Several reports describe the same failure: the server accepts a thread or reply, but the text remains in the composer or returns after navigating Back. Sometimes it clears only after a second submission. This invites accidental duplicate posts. The Clear fields control is a workaround, not a resolution.
Original reports collected in the feedback register:
- https://zenmemes.com/posts/thread-20261018031322-3938ec36
- https://zenmemes.com/posts/reply-20261018031358-f5bdd2dd
- https://zenmemes.com/posts/thread-20261021100330-f5d989b4
- https://zenmemes.com/posts/thread-20261021101311-4637e338
- https://zenmemes.com/posts/reply-20261023053718-65ba1069
Later discussion: https://zenmemes.com/threads/thread-20261105152720-835ca59c (posting and drafts, including submitted draft retention and safe retries). A November 9 Activity reply explicitly asks the server's successful acceptance to clear stored draft state regardless of navigation.
Canonical issue: docs/feedback/items/PF-20261030-B03.txt in https://github.com/gulkily/v3
Current engineering status: A proposed fix is already on https://github.com/gulkily/v3/tree/fix/duplicate-post-submissions. It handles Back navigation, interrupted/uncertain responses, and repeated attempts for JavaScript anonymous threads and replies. Its recorded local checks passed (528/528, including Chrome browser tests), but it has not been merged or production-verified. The review explicitly leaves Firefox/Safari, no-JavaScript duplicate retries, and production confirmation outstanding. Duplicate posts were initially a suspected consequence, not independently established as the cause of each original report.
Deployment decision required: the branch assigns random permanent IDs to new anonymous posts rather than date-derived IDs; the maintainer should review that durable format choice before merge. See docs/plans/duplicate_post_submissions/duplicate_post_submissions_review_findings.md on the branch.
Acceptance checks: submit a thread and a reply; observe server acceptance and an empty composer on return/Back (including bfcache and full reload); repeat clicks and retry after a lost response must not create another post; a failed submission must retain its draft; text newly edited after an accepted submission must not be erased; explicit URL prefills must survive. Verify on iPhone Safari as well as desktop browsers.