Open riyazuddinsyed opened 2 days ago
The reason for this is the way "unsaved changed" functionality is implemented -- the user has made changes, and undoing them doesn't clear the flag.
This could be better, but Mihai and Jacqueline believe the user will figure this out and click "exit".
This change should apply to all local filings.
Describe the bug in the current situation
When a user makes changes to filings, such as COD/COA, and then reverts those changes, leaving the filing in its original state, clicking "Cancel" still triggers a pop-up warning that unsaved changes will be lost. This behavior is unexpected since the filing has been restored to its original state.
Steps to reproduce the behavior:
Screenshots/ Visual Reference/ Source
Private Zenhub Video