4 ms·
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 se
by pault 9y ago
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.
- Snappy 9y agoMy 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.
- stevekemp 9y agoSame 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.