Opened 10 years ago
Last modified 2 years ago
#36479 new defect (bug)
Improve autosave in the browser
| Reported by: | azaozz | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Autosave | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
Several improvements that can make this quite better:
- Try to better detect when a restore may be needed.
- Make in-browser autosaves a "higher priority" than remote/server autosaves. The in-browser content is fresher. If both are available, prefer/emphasis the in-browser data.
- Add some subtle, always present UI for restoring a post from in-browser autosave. This should (probably) be only available before the users start typing.
- Consider adding the in-browser data to the revisions or display a preview/diff with the current data in some other way.
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)