Community
Participate
Working Groups
Add support for "implicit" editor saving if auto-save is on. Namely: * Automatically save the editor if the user clicks on the close button or an action - without asking for confirmation. * Don't show the dirty mark on an editor. * Disable the revert action.
(In reply to Bruno Medeiros from comment #0) > Add support for "implicit" editor saving if auto-save is on. Namely: > > * Automatically save the editor if the user clicks on the close button or an > action - without asking for confirmation. > * Don't show the dirty mark on an editor. -1 > * Disable the revert action. -1
Why a -1 to those changes? What's helpful about the dirty editor mark if auto-save is on? At this point it becomes just a indicator of internal state, not useful to a regular user. It's likely even more annoying if the user wants to have lower auto-save delay than the default. As for the revert action, having that action enabled allows for a race condition to occur - the user invokes revert but the autosave save was triggered in the meanwhile, and the revert fails.
To follow up on this, I don't really care much about what is done to the Revert action: I don't expect users will be using it if auto-save is on, so in practice it doesn't matter much either way. But the editor dirty mark is problematic. I think it's important to able to get rid of it, at least with an additional preference. Would that not be acceptable? BTW, I'm thinking of submitting a patch for this issue.
(In reply to Bruno Medeiros from comment #2) > Why a -1 to those changes? > What's helpful about the dirty editor mark if auto-save is on? At this point > it becomes just a indicator of internal state, not useful to a regular user. > It's likely even more annoying if the user wants to have lower auto-save > delay than the default. And it's even more useful if the user wants to have a higher auto-save delay.
