-
Notifications
You must be signed in to change notification settings - Fork 751
Signature component not working as expected on "Disabled" mode #1764
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
Comments
Thankyou for your response. But from the video, I see that after making the initial submission, the component is not changed to disabled state here. The issue is when we are trying to edit a submission when the component is in disabled mode. Can you please make that change and see how the form field is behaving? |
Thank you for reporting this. I was able to reproduce your issue. I have logged a ticket for review by our planning team. In the meantime, we are always willing to review any contributions to resolve this behavior. Internal reference: FIO-8677 |
Thankyou for your update. Could you give us an approx. ETA by when we can get some update from the team again? |
After planning review we do not expect to resource this a developer in the near future. We would happily review any PRs that might resolve this behavior in our open source, though I suspect this might not be related to our open source libraries. If this is a particular priority for you I would suggest going through our support channels and communicate with support@form.io |
Describe the bug
When a form submission is made and trying to edit the submission, even after setting a particular signature component in disabled mode, we are still able to access the component and is taking new edits for one click.
Version/Branch
v8.5.0: formiojs@4.19.0
To Reproduce
Steps to reproduce the behaviour:
Formio.signature.component.mp4
The text was updated successfully, but these errors were encountered: