Amazingly it's 2018 and it seems neither Github nor Chrome nor Firefox remember text you've typed for 40 minutes into a text area in a tab if you accidentally close the tab. How is this a thing?
5
4
1
19
Relevant Github bug: github.com/isaacs/github/iss… I can't find the relevant browser bug. It seems a shortcoming though!

Save drafts of comments Β· Issue #376 Β· isaacs/github

Excerpt from my mail to support@github.com I'd like to raise a feature request: save drafts of comments during the time they're written (as StackOverflow does with posts, BTW). I have often...

github.com
1
It's over 20 years ago I read UX books that quite clearly explain this isn't acceptable. And it just requires a relatively small feature in any of several products to do better than now, and the rest of UX has improved loads. Yet still...
1
1
Replying to @frabcus
These days, browsers have to treat pages as independent applications. Essentially it's up to those applications to support some sort of recall-draft if their inputs ought to support it. I suppose you could write an addon which uses local storage to do that kind of thing though.

Jul 12, 2018 Β· 3:40 PM UTC

1
Replying to @dsilverstone
I take your point... But this particular example could be solved by "undo close tab" restoring the exact state. I'd like to see the bug tracker discussion about all the options.
1
1
Requires close-tab to serialise the state of *every* JS context associated with the tab, and JS was not designed to support state serialisation in quite that fashion. Essentially it'd mean closing tabs didn't free memory for quite some time which would be risky.
1
more replies