You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so, along with #1598 , this also caused me to lose work.
It's not entirely a bug, but, more of a feature request, and users should never lose work!
Well I generally stare at the preview mode while blogging. One time, I had written a lot, and then automatically clicked the preview and hit backspace, my brain fooled into thinking that was my editor. My browser went back and I lost work.
For one thing, it would be nice if the page loaded with the article data in place, so if you did go back and forward, default browser functionality would potentially keep your work. This would probably fix #1598 too, as long as you used the same window.
Since it seems the article is populated after page load, then you really need to stop users from being able to willy nilly go back, especially since they could have written a lot.
The text was updated successfully, but these errors were encountered:
Thanks for posting this, we're very much aware that it's a big issue and it's not one we've over looked.
We have implemented a basic fix in the latest master (I assume you're using 0.3.3), whereby the editor won't let you leave if you have unsaved changes #1331 and we are planning to add autosave #1413 in 0.5.
Really appreciate you getting involved here on GitHub, but it would be lovely if you wouldn't mind taking a few minutes to read our contributing guidelines. Have a little look around our GitHub issues, our wiki, the Roadmap and Planned Features listing. You'll find we've made an awful lot of progress since 0.3.3.
so, along with #1598 , this also caused me to lose work.
It's not entirely a bug, but, more of a feature request, and users should never lose work!
Well I generally stare at the preview mode while blogging. One time, I had written a lot, and then automatically clicked the preview and hit backspace, my brain fooled into thinking that was my editor. My browser went back and I lost work.
For one thing, it would be nice if the page loaded with the article data in place, so if you did go back and forward, default browser functionality would potentially keep your work. This would probably fix #1598 too, as long as you used the same window.
Since it seems the article is populated after page load, then you really need to stop users from being able to willy nilly go back, especially since they could have written a lot.
The text was updated successfully, but these errors were encountered: