Issue Description
After hitting the "Next" button on the second screen of the Send for Signatures flow, a small modal pops up that says "Are you sure you want to send?" If you click the X button, instead of canceling and closing the modal, it advances the document to the "Sent" state anyway.
Expected Behavior
A confirmation dialog should actually cancel the thing when the user clicks the button to cancel the action.
Current Behavior
It advances the document to the "Sent" state anyway, showing "SENT" for all recipients without actually sending the emails.
Steps to reproduce
- Log into app.opensignlabs.com
- Click Request signatures.
- Fill out steps 1 and 2.
- Click "Next" after setting fields.
- Click the X button on the confirmation dialog.
- Die a little inside.
Screenshots of the issue(optional)
No response
Operating System [e.g. MacOS Sonoma 14.1, Windows 11]
No response
What browsers are you seeing the problem on?
Chrome
What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]
Whatever is currently deployed in production
What environment are you seeing the problem on?
No response
Please check the boxes that apply to this issue report.
Code of Conduct
Issue Description
After hitting the "Next" button on the second screen of the Send for Signatures flow, a small modal pops up that says "Are you sure you want to send?" If you click the X button, instead of canceling and closing the modal, it advances the document to the "Sent" state anyway.
Expected Behavior
A confirmation dialog should actually cancel the thing when the user clicks the button to cancel the action.
Current Behavior
It advances the document to the "Sent" state anyway, showing "SENT" for all recipients without actually sending the emails.
Steps to reproduce
Screenshots of the issue(optional)
No response
Operating System [e.g. MacOS Sonoma 14.1, Windows 11]
No response
What browsers are you seeing the problem on?
Chrome
What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]
Whatever is currently deployed in production
What environment are you seeing the problem on?
No response
Please check the boxes that apply to this issue report.
Code of Conduct