Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Sauvegarde] - voir quand on envoi les données #157

Closed
laurentC35 opened this issue Nov 15, 2024 · 2 comments
Closed

[Sauvegarde] - voir quand on envoi les données #157

laurentC35 opened this issue Nov 15, 2024 · 2 comments

Comments

@laurentC35
Copy link
Contributor

laurentC35 commented Nov 15, 2024

  • au clique sur une page autre qui "ferme" l’orchestrateur (plan du site) ?
  • ALT+F4: fermeture du navigateur -> proposé une pop-up du type 'êtes-vous sûr de quitter la page ? vous allez perdre de la donnée...'
  • autre ?
  • toute les X secondes

Un peu lié à #149, techniquement voir ce qui est possible de faire

@chloe-renaud
Copy link
Contributor

We can use this hook: https://react-hooked.vercel.app/docs/useBeforeUnload

Currently, the user can potentially lose some data if they quit their page since the save is only done on manual disconnect, navigating through internal links and clicking next or previous inside the orchestrator.

If they close their navigator or tab no data can have been saved since a while, which can be annoying to the user.
They can also lose data if their computer suddenly shuts down.

We can either ask the user if they truly want to close the tab since they can lose data (which cover the first case) and/or save the data from time to time when we see the data has been changed and has not been saved in a while (which cover the second case).

@JulienCarmona
Copy link
Contributor

Je fais une story. Très bon sujet https://github.com/InseeFr/Concevoir-Workplace/issues/62

On va partir sur la gestion du dirty state

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants