News for hackers. Stuff that matters.
Re:GitLab 10.4 released by pault on Tuesday January 23, 2018 @11:49AM (#16214968)
I started using gitlab yesterday and during one merge request cycle I managed to lose my textfield contents several times. Keeping form contents backed up to session storage is a trivial task and it's maddening that they haven't implemented it in an area where you might be spending 20 minutes writing a comment then lose it when you change some value in a select menu. Really bad UX. Changing a merge target shouldn't require a full page refresh.
Re:GitLab 10.4 released by Snappy on Tuesday January 23, 2018 @12:29PM (#16215342)
My issue comment drafts are always persisted locally and not lost on refresh. Not sure why you're seeing otherwise. It is supposed to work that way. If you're seeing otherwise, please consider opening an issue.
Re:GitLab 10.4 released by stevekemp on Tuesday January 23, 2018 @12:47PM (#16215506)
Same here. I often force-reload issues/merge-requests because I see a popup "Press Ctrl-Enter to submit" which won't disappear, and obscures the content I'm trying to write/preview.

I've been pleased the text-content persists.