Skip to content

make users aware of unsaved changes #175

@hofstef

Description

@hofstef

Is your feature request related to a problem? Please describe.

Unsaved changes are easily overlooked because they are only indicated by a change of the color of the export button.

When the story is "removed" (by importing another story, by clearing the canvas by creating a new story, or by closing the browser/tab), unsaved changes will be lost. Users are not made aware that they will lose unsaved changes unless they export the current story.

The autosave feature does not fully prevent this problem for two reasons:

  • Autosave is triggered every X secons and you would have to be lucky that it was triggered between the last change and removing the story
  • Even if the last version was autosaved, it only exists in the local browser storage. The users will be unaware that the version on their local file system is not current.

Describe the solution you'd like
Perhaps a modal dialog that asks the user if they want to export the story or cancel whatever they triggered (import story/new story/close browser).

Describe alternatives you've considered

  • triggering autosave on import/new story/close browser: User is still not aware that their exported file is not up-to-date (see above).
  • visually more prominent "dirty" indicator: Could still be overlooked.

Additional context
bpmn.io uses modal dialogs to solve this problem

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureconcrete new feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions