flowable / flowable/flowable-engine
Warning for losing unsaved work in process modeler doesn't always show
- Langage dominant
- Java
- Étoiles
- 9.5k
- Forks
- 2.9k
- Merge moyen
- 7 h 8 min
- PR mergées (30 j)
- 2
Description
**Describe the bug**
Due to the nature of navigation (using the "#"), the `onbeforeunload` hook to warn users about abandoning unsaved work does not work when navigating via buttons or hyperlinks inside the modeler. If you use regular, in-modeler navigation, like eg. closing the model or clicking on one of the links to other designers (like the Forms designer), you don't get a warning and lose your work. Going back to the process model just shows you the last saved version again and all work is lost. You do get the warning when you go to another site (from the address bar or a bookmark) or do a full refresh of the page but the hash-navigation ("the single page app way") doesn't trigger the hook, thus no warning, thus possibly losing unsaved work. The old flowable-explorer didn't use this manner of navigation so this problem didn't occur there.
**Expected behavior**
So whenever you edit a model and make the slightest change, the onbeforeunload hook should be added but also a hook to the hash-navigation-framework that is used to display a custom warning prompt. If not possible I guess Flowable should shelve the changes (eg. on localstorage) and gives the possibility to start working from those shelved changes instead of the ones saved in the DB.
**Additional context**
Flowable 6.5.0.6
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par la gestion de onbeforeunload du modeleur de processus et du framework de navigation par hash, puis reproduisez la navigation dans le modeleur et via des liens vers d’autres designers après avoir effectué une modification. C’est terminé lorsque la navigation interne affiche un avertissement personnalisé concernant les modifications non enregistrées et ne les supprime pas, tandis que l’avertissement existant pour la navigation externe et l’actualisation continue de fonctionner.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- frontend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100