This repository has been archived by the owner on Jul 23, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 400
unsaved changes prompt not triggered when user does autoregeneration of a password field #761
Comments
Thanks @JCDuclare for the opened issue, the video was handy. I can replicate this on my mac system as well. My first assumption is that there is an event that triggers when the view is actually edited but in this instance the generate password button does not cause that event to get triggered. I'll look into this issues. |
@gryffs This would be a good candidate for a PR if you'd like to tackle it! |
gryffs
added a commit
to gryffs/desktop
that referenced
this issue
Apr 22, 2021
This issue is also mentioned here: #563 |
eliykat
added a commit
that referenced
this issue
May 2, 2021
Implement the markAsDirty form controls for AddEditComponent(#761) Prevents add-edit page from closing if new password has been generated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Normally, when the user tries to leave the edit process of e.g. a login object the desktop app will create a prompt with a warning for unsaved changes. This does not happen if the user triggers an autoregeneration of a password field and then leaves the object.
Steps To Reproduce
Expected Result
'Unsaved Changes' warning is triggered and the user has to confirm to leave and discard the changes
Actual Result
Changes are instantly lost and the user has been given no warning
Screenshots or Videos
Environment
The text was updated successfully, but these errors were encountered: