A bug has been discovered in Discourse. When composing a reply, switching to offline mode, and then pressing the reply button, the reply gets stuck with the saving message spinner forever and never gets posted jidanni.
jidanni found that the only way to resolve this issue is to discard the edit.
However, HamMan2118 discovered that refreshing the page will save the draft. jidanni expressed concern that users might not want to take this risk, as refreshing the page could potentially result in lost work.
HamMan2118 pointed out that Discourse auto-saves drafts, allowing users to close the tab and pick it up later. HamMan2118 also shared a video demonstrating the bug and the fix.
jidanni noted that refreshing the page without an internet connection could be catastrophic, suggesting that the program should either automatically refresh the page when the connection is restored or provide a refresh link for the user to click when they notice their connection is back.
Try this test. Compose a reply to some thread. Okay now switch your cell phone to offline. Now press the reply button to send the reply. Now turn your network back on. The reply gets stuck with the saving message spiiner forever and it never gets posted.
That’s good to know. Except usually when we’re worried something will get lost, the last thing we want to do is push the refresh button! Yes I trust you it’ll have a happy ending, but most users wouldn’t want to take the risk.