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
If users close the composer and there are unsaved changes, they are prompted: "Discard changes to draft? In this case, wouldn't it make sense to automatically save the draft once more without asking the user?
If people are used to autosafe, they don't understand why they are sometimes asked to discard changes, and sometimes not, if by chance the last autosafe happened just before they decided to close the composer.
The text was updated successfully, but these errors were encountered:
If I have a draft but for some reason delete everything in the content and close the composer, autosave will still keep a feasible version. I'm not sure that this would improve the UI, but I'm also not firm in that opinion
If I have a draft but for some reason delete everything in the content and close the composer, autosave will still keep a feasible version.
Not if you are unlucky and autosave hits you just after deleting the content and just before closing the composer.
It should not be a roulette game, which version of your content is saved or if you have the opportunity to reconsider your last action. If you want to protect users from the consequences of careless deletions, you should offer to always save the last three autosafes, Flarum's version of the time machine so to speak ;)
If users close the composer and there are unsaved changes, they are prompted: "Discard changes to draft? In this case, wouldn't it make sense to automatically save the draft once more without asking the user?
If people are used to autosafe, they don't understand why they are sometimes asked to discard changes, and sometimes not, if by chance the last autosafe happened just before they decided to close the composer.
The text was updated successfully, but these errors were encountered: