pull down to refresh
719 sats \ 3 replies \ @cointastical 28 Nov 2022 \ on: Daily discussion thread
I cannot be the only one that runs into this. I compose a lengthy comment reply, or composing a longform post, and somehow I accidentally press something or for whatever reason (e.g., browser crash ?) my chrome browser has closed.
And with it gone is my content that I had just spent a fair amount of time writing.
SN does have session local storage, so if I close a tab accidentally, I can recover by simply going back to the post I was composing or the one to which I was replying. But when the browser goes bye-bye, there's no recovery.
This has happened to me numerous times. Maybe I see this more than others because I almost always use Incognito mode/private browser, and thus there is no session local data saved to recover from when re-launching my browser.
So my request is for a method to explicitly be able to click Save for my draft so that I can recover it across sessions, (or maybe a periodic automatic save to SN's back-end, like after every ten seconds following edit activity, or something like that).
One thing I could do instead is hit the Post or Reply button with a draft maybe close enough to justify publishing, but then I only have ten minutes to edit/revise what I wrote, which is a problem, where a possible solution has not yet been implemented. So I really don't want to hit Post or Reply until I have the content that I am composing to be truly ready for submitting.
I've created an Issue with this feature request in Github, Issue #216, but wanted to ask this here:
Am I the only one that keeps having this problem with losing work when composing for SN?
Try brave
reply
Fwiw, this has never happened to me- is this just on SN or on other sites as well? chrome is a certainly a terrible memory hog...
reply
Has the browser closed without my intending for it to happen, with other sites? Yes.
It hasn't happened often enough where I have been able to figure out if it is something I did just prior to this happening, and thus it was my actions as the cause, or if it was a crash and the browser just disappeared. I have a touchpad that I'm always bumping as I type causing the mouse to click somewhere where I didn't intend. If that's the cause (e.g., clicking the X to close the browser), then I wish Chrome would let me configure it to make me confirm that I really want to close the browser (even if I have multiple tabs open).
reply